# Basic information

> This document is mainly used to explain endpoints usage, illustrate with code examples for requesting endpoints, specific interface input parameters and output parameter information

### Important notice

{% hint style="info" %}
The request code examples in this document are using Axios
{% endhint %}

{% embed url="<https://www.npmjs.com/package/axios>" %}

#### LOGO: <https://images.allchainbridge.com/dex/CrossChainX.svg>

### Contract Address

{% hint style="info" %}
Currently Bridgers supports any currency exchange that has been supported on the 17 listed chains. The following are the contract addresses of each chain
{% endhint %}

1. eth mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
2. bsc mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
3. polygon mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
4. tron mainnet contract address：THFFjqc393iiLgdgVW3vV748zFgBvyCVFn
5. arbitrum mainnet contract address: 0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
6. avalanche mainnet contract address: 0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
7. optimism mainnet contract address: 0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
8. cronos mainnet contract address: 0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
9. solana mainnet contract address: ravonxmJTD3Ex9kyJFKDD5uqRbsrszzPHPPhgaVbHav
10. sui mainnet contract address: 0x2d77f3281429472c1e3d004801d8b5be250e64878e10bf2ecd71dfe351cdab5d
11. BASE mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
12. ZKSYNC mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
13. zkEVM mainnet contract address：0xe5934c17cf172b83a4f5f4f8a94385ec0ef48537
14. TON mainnet contract address: EQBNEO5gGVMGGwUv7akYqGaPM\_W9IFLFOCV6AHi445PFumB3
15. BTC mainnet address: bc1qflxvf27m4hwzjtamcntjvadcukl86rfheuzsep
16. DOGE mainnet address: DFVcavxwfgmeLGxVNwMtvrxmyQ96nwjhs6
17. LTC mainnet address: ltc1q7dnm064kvg6kavecdkkp65qgufsampcwn6qtw6


---

# Agent Instructions: 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://docs-api-en.crosschainx.io/basic-information.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.