> For the complete documentation index, see [llms.txt](https://nucleus-ai.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nucleus-ai.gitbook.io/whitepaper/core-features/4.-core-platform-features/4.6-multi-chain-support.md).

# 4.6 Multi-Chain Support

Nucleus AI was built to be chain-agnostic. Builders can choose the chain that fits their needs—whether for speed, fees, or ecosystem alignment.

Currently supported:

* Ethereum (Mainnet and Testnets)
* BNB Chain
* Polygon
* Solana
* Arbitrum
* Optimism
* Avalanche
* Fantom

Each smart contract template is customized for the selected chain. From address formatting to gas handling, everything is pre-configured to ensure seamless deployment. In future updates, Nucleus AI will allow cross-chain token bridges, NFT minting, and more advanced multi-chain operations.


---

# 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://nucleus-ai.gitbook.io/whitepaper/core-features/4.-core-platform-features/4.6-multi-chain-support.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.