> For the complete documentation index, see [llms.txt](https://monoprotocol.gitbook.io/monoprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monoprotocol.gitbook.io/monoprotocol/architecture/supported-networks.md).

# Supported Networks

Mono Protocol is designed for universal blockchain support, starting with major networks and expanding to include emerging ecosystems.

Chain Support: Mono Protocol is constantly expanding network support. Each network in Mono Protocol is identified using the CAIP-2 chain ID format.

| Chain ID         | Status                  |
| ---------------- | ----------------------- |
| Ethereum Mainnet | ✅                       |
| Optimism         | ✅                       |
| Arbitrum         | ✅                       |
| Polygon          | ✅                       |
| Base             | ✅                       |
| Linea            | ✅                       |
| Avalanche        | ✅                       |
| BSC              | ✅                       |
| Blast            | ✅                       |
| Berachain        | ✅                       |
| Solana           | ✅ Beta                  |
| Bitcoin          | TBD                     |
| Other EVMs       | On demand               |
| Other Chains     | On demand, case by case |

Network References:

// Example of referencing Ethereum in the API

const ethereumChain = 'eip155:1';

<br>


---

# 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:

```
GET https://monoprotocol.gitbook.io/monoprotocol/architecture/supported-networks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.