1 of 2

Bridge ID

Bridge ID helps expand.network to redirect the query or transaction to the appropriate bridge protocol. By default, it tries to communicate with the Stargate mainnet. Following is the list of Bridge with their respective IDs.

Bridge Name

Bridge ID

Chains Supported

Internal Chain Ids for Bridge

1. Stargate

Chain Name

Chain Id

2. Squid Router

Chain Name

Chain Id

Bridge ID

Bridge Name

Bridge ID

Chains Supported

Mainnet Chains supported: Ethereum, Binance, Avalanche, Polygon, Arbitrum, Fantom, & Optimism
Testnet Chains supported: Ethereum(Goerli), Polygon(Mumbai)

Mainnet source chains supported: Ethereum, Arbitrum, Optimism, Avalanche, Polygon, Binance, Fantom.
Mainnet destination chains supported: Ethereum, Arbitrum, Optimism, Avalanche, Polygon, Binance, Fantom, Linea, Base, MoonBeam, Mantle, Celo, Kava, Filecoin, Osmosis, Cosmoshub, Kujira, Neutron, Stargaze, Axelarnet, Umee, Persistence, Sommelier, Stride, Crescent, Juno, Carbon, Regen, Agoric, Chihuahua, Akash, Comdex, Archway, Quicksilver, Omniflixhub, Migaloo, Mars, Terra, Assetmantle, GravityBridge, Bitcanna, Bitsong, Cheqd, Decentr, Desmos, Irisnet, Impacthub, Jackal, Likecoin, Lumnetwork, Sentinel.
Testnet source chains supported: Ethereum-2, arbitrum, avalanche, polygon, binance, fantom.
Testnet destination chains supported: Ethereum-2, arbitrum, linea, avalanche, mantle, moonbeam, filecoin, polygon, binance, fantom, celo, osmosis-6, axelarnet, kujira, sei, fetch, evmos, comdex, aura.