> 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/blockchains-infras.md).

# Blockchains Infras

Vishwa is chain agnostic — designed to orchestrate assets and credit flows across any blockchain. Our orchestration engine abstracts away chain-specific complexity, allowing assets, borrowers, and liquidity providers to interact seamlessly across ecosystems.\
\
By integrating with Vishwa, chains can:

* Unlock New TVL Growth – Orchestrated lending flows and stablecoin-backed credit lines bring significant capital inflows, boosting on-chain activity.
* Attract Institutional & Retail Liquidity – By becoming part of Vishwa’s network, chains open themselves up to global stablecoin liquidity and agentic lending demand.
* Expand Ecosystem Utility – Credit and lending flows create new use cases for native assets, stablecoins, and RWAs, driving higher engagement for applications built on these chains.

<figure><img src="/files/OG0CwtGbWnJXdthgqaXT" 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/blockchains-infras.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.