Skip to main content
Addresses of the core contracts deployed on BOT Chain. Every BOT Chain address below was checked on BOTScan on 2026-10-01: each one holds verified contract code under the expected name.
Always copy addresses from this page or from BOT Chain’s docs, never from a token list or a search result. Other tokens named “USDT” exist on testnet, with different addresses and decimals.

​
Mainnet (chain 677)

V2 pair init code hash (mainnet): 0xa075aa7c03cb5559a4c6202459721232c21e18148152410f6beec063e8499e6c

​
Testnet (chain 968)

V2 pair init code hash (testnet): 0x9d2cc5d1f5560e2a4119c794e0fa625b8c50af562e72436c234ec1addb77de47 The V2 contracts and init code hashes differ between networks. The V3 contracts share addresses.

​
Bridge gateways on other chains

The BOT Chain bridge uses a gateway contract on each connected chain. These addresses come from BOT Chain’s Bridge contract addresses page.

​
Mainnet routes

​
Testnet routes

USDT has different decimals on different chains. Convert amounts when you move between them.

​
Resource IDs

The bridge identifies each asset by a resource ID. This value comes from BOT Chain’s docs and was not checked on chain.

​
Check an address yourself

Ask BOTScan for the contract’s name and whether its source is verified:
check-address.sh

Networks

Chain IDs, RPCs and explorers.

BDEX API

Pools, pairs and tokens over HTTP.
Last modified on October 2, 2026