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

# Supported Blockchains

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

CryptoCart supports a variety of blockchain networks to accommodate different customer preferences and expand its reach. This multi-chain support allows us to tap into different networks and attract customers from various blockchain communities. To date, we currently support 10 different chains and have plans to roll out a lot more in the near future. We currently support:

* **Ethereum Chain**
* **Binance Smart Chain**
* **Polygon Chain**
* **Metis Chain**
* **Avalanche Chain**
* **Solana Chain**
* **Optimism Chain**
* **Arbitrum Chain**
* **Base Chain**
* **Tron Chain**

Payments across all supported chains are completely automated. This means when a user makes a payment with their preferred cryptocurrency on their preferred blockchain, the system automatically processes the transaction, verifies it, and completes the purchase within a matter of minutes.


---

# 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.cryptocart.cc/ecosystem/supported-blockchains.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.