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

# NerveNetwork Integration Chains Guide

### Introduction

NerveNetwork relay provides efficient and secure cross-chain bridge services for different blockchain networks. By integrating your network with NerveNetwork, you will be able to:

* Bridge your native assets to other mainstream blockchain networks;
* Enable other blockchain assets to be bridged into your network;
* Establish liquidity pools between your chain’s assets and assets from other chains;
* Support cross-chain swaps and asset management.

NerveNetwork cross-chain channels are already integrated into multiple bridge products. Once your network is integrated, you can easily leverage these products to provide cross-chain swap and bridging services for your assets.\
\
Currently supported NerveNetwork channel swaps/bridges:\
Nabox Wallet: <https://nabox.io/>\
SwapBox: <https://swapbox.io/>\
DODO: <https://app.dodoex.io/>\
Bridgers: <https://bridgers.xyz/>\
MetaPath: <https://www.metapath.me/>

***

### Integration Process

#### 1. Submit Integration Request

* Contact the NerveNetwork business and technical team to confirm the integration requirements.
* Contact information: <https://id.nabox.io/profile?ID=nerve>
  * Telegram: [@Nervego](https://t.me/Nervego)
  * Email: <support@nerve.network>

#### 2. Donation & Scheduling

* Integration & Maintenance Fee: A donation of 20,000 USD equivalent in $NVT is required.
* Integration priority is determined by donation amount. Higher donations receive earlier scheduling.
* Once the donation is confirmed, our developers will arrange the integration schedule.<br>

#### 3. Technical Integration

* Provide relevant developer documentation and SDKs of your network.
* Collaborate with the NerveNetwork team to complete module integration and testing.

#### 4. Code Audit

* If your blockchain is based on a new or unsupported technical architecture, you are required to provide a third-party security audit report after the integration is completed.
* This ensures the safety and stability of cross-chain interactions.<br>

#### 5. Mainnet Launch

* After successful testing and validation, your network will be officially supported on NerveNetwork mainnet.
* NerveNetwork will publish an official announcement to the community and partners to enhance the visibility and liquidity of your chain’s assets.

***

### Benefits of Integration

* One-stop cross-chain bridge solution, connecting your assets with multiple mainstream blockchains.
* Cross-chain swap functionality, expanding use cases for your assets.
* Access to NerveNetwork’s established cross-chain ecosystem and liquidity.
* Ongoing technical support and maintenance from NerveNetwork.

***

### Contact Us

* Telegram: [@Nervego](https://t.me/Nervego)
* Email: <support@nerve.network>
* Website: <https://nerve.network>


---

# 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://nervenetwork.gitbook.io/nerve/nervenetwork-integration-chains-guide.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.