> For the complete documentation index, see [llms.txt](https://docs.vishwalab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vishwalab.com/ecosystem/collateral-asset-sources.md).

# Collateral Asset Sources

The foundation of Vishwa’s credit ecosystem is built on diverse and high-quality sources of collateral. By orchestrating collateral from miners, institutions, and real-world asset issuers, Vishwa ensures that lending markets are both secure and scalable. Our trustless orchestration layer abstracts away multi-chain complexity, enabling these assets to flow seamlessly into productive credit lines while providers retain custody and transparency.

## BTC Mining Partners

> "Vishwa has been a game changer for us. We are able to use the stablecoin liquidity to pay our 7-digit utility bills without selling our BTC mined or any custodial risk. This is the most innovative product in this field since 2016." \
> \
> &#x20;                                                                             — Mason Jappa, Founder and CEO of Blockware

Our mining partners contribute Bitcoin as a productive asset class. Through Vishwa, miners unlock stablecoin-backed credit lines while retaining custody of their BTC — enabling liquidity without forced liquidation.

<figure><img src="/files/hhgFI0SXn2NW9V0wLduR" alt=""><figcaption></figcaption></figure>

## Institutional Digital Assets Holders

Institutions with large holdings of Bitcoin and Ethereum can deploy their crypto productively through Vishwa. By posting assets as collateral, they gain access to stablecoin-backed credit lines for liquidity needs while simultaneously earning yield on their treasuries — all without giving up custody.

For those requiring compliant custody, Vishwa partners with regulated custodians such as Anchorage Digital to provide seamless custodial integration into orchestrated lending and yield markets.

<figure><img src="/files/TjiBkqsx9NmitSWTJc1m" alt=""><figcaption></figcaption></figure>

## RWA and Tokenized Securities Issuers

Issuers that bring equities, bonds, and other real-world assets on-chain expand the pool of available collateral. Vishwa abstracts away the complexity of managing tokenized RWAs across chains, enabling their seamless use in lending strategies and credit markets, and bridging traditional finance with decentralized liquidity.

> Vishwa is the missing link for us. By pairing our RWA origination with their non-custodial orchestration layer, our tokenized assets instantly become productive collateral across on-chain and off-chain liquidity. This partnership unlocks scale and access we couldn’t achieve alone.\
> &#x20;                                                                                                            — Bridget Li, Founder of Asseto&#x20;

<figure><img src="/files/nmgkpKY4wWftexYZH0Y2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vishwalab.com/ecosystem/collateral-asset-sources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
