> For the complete documentation index, see [llms.txt](https://docs.wagon.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wagon.network/wallet-and-blockchain/supported-networks.md).

# Supported Networks

Wagon Network currently supports multiple blockchain networks to ensure seamless access, low-cost transactions, and reliable infrastructure for DeFi lending and data tracking.

## ✅ Live Networks

* **BNB Smart Chain (BSC)**
  * Fast, low-cost, and EVM-compatible.
  * Chosen for its **low fees**, **reliable uptime**, and **strong ecosystem support**.
  * Integrates directly with **IDRX stablecoin** for on-chain lending and repayments.
* **Base**
  * A secure Ethereum Layer 2 (L2) network built by Coinbase.
  * Offers scalability and reduced gas costs.
  * Integrates directly with **IDRX stablecoin** for on-chain lending and repayments.

> Users can switch between supported networks via their wallet. Wagon will automatically detect the correct network and prompt the switch if needed.

## 🛠 Why Multi-Chain?

* Enhance accessibility for users across different ecosystems.
* Leverage low fees and scalability on Layer 2 chains.
* Provide redundancy and flexibility for future DeFi integrations.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wagon.network/wallet-and-blockchain/supported-networks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.