> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/mayachain-dev-docs/protocol-development/adding-new-chains.md). # Adding New Chains Chain Developers should be extremely familiar with how MAYAChain works, and how their own chain works. There is now a specific process for the addition of new chains, see: ​ #### Process 1. Read ​ 2. Bifrost: Start by forking one of the existing [Bifrosts](https://gitlab.com/mayachain/mayanode/-/tree/develop/bifrost/pkg/chainclients?ref_type=heads) (UTXO, EVM or COSMOS). 3. Daemon: Add the chain daemon to MAYAChain/Node-Launcher: 4. Smoke Tests: Build out the smoke tests for the chain. This ensures the connection is robustly tested. 5. [XChainJS](https://github.com/xchainjs/xchainjs-lib): Add a new chain package to XChainJS so the entire ecosystem of wallets can easily support. Once this is complete, the chain can be added to Stagenet. After some time of demonstrating Stablity on Stagenet, the MAYAChain Node Operator community is polled and if supported, it can be merged to Mainnet. Once on mainnet, the chain is typically given a period of 12 months to demonstrate uptake and usage. If the chain cannot maintain sufficient demand, it may be removed from the network and all liquidity refunded to LPs. --- # 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.mayaprotocol.com/mayachain-dev-docs/protocol-development/adding-new-chains.md?ask=&goal= ``` `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.