# Bridge IDs

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. 

<table><thead><tr><th width="148">Bridge Name</th><th width="128.67578125">Bridge ID</th><th width="431">Chains Supported</th></tr></thead><tbody><tr><td>Stargate </td><td>100</td><td><ol><li><strong>Source chains supported</strong> : Ethereum, Optimism, Binance Smart Chain, Polygon, Fantom, Mantle, Base, Arbitrum, Avalanche, Linea</li><li><strong>Destination chains supported</strong> : Ethereum, Optimism, Binance Smart Chain, Polygon, Fantom, Metis, Kava, Mantle, Base, Arbitrum, Avalanche, Linea</li></ol></td></tr><tr><td>Allbridge Classic</td><td><ol><li>Mainnet: 300</li></ol></td><td><ol><li><strong>Source chains supported :</strong> Ethereum, Binance Smart Chain, Polygon, Fantom, Stellar, XRP Ledger, Avalanche</li><li><strong>Destination chains supported</strong> <strong>:</strong> Ethereum, Binance Smart Chain, Fuse, Polygon, Fantom, Solana, Near, Stellar, XRP Ledger, Stacks, KOII, Kaia, Celo, Avalanche, Harmony</li></ol></td></tr><tr><td>Allbridge Core</td><td><ol><li>Mainnet: 400</li></ol></td><td><ol><li><strong>Source chains supported :</strong> Ethereum, Optimism, Binance Smart Chain, Sui, Polygon, Solana, Tron, Stellar, Base, Arbitrum One, Avalanche C-Chain</li><li><strong>Destination chains supported</strong> <strong>:</strong> Ethereum, Optimism, Binance Smart Chain, Sui, Polygon, Solana, Tron, Stellar, Base, Arbitrum One, Celo, Avalanche C-Chain</li></ol></td></tr><tr><td>Stargate V2</td><td><ol><li>Mainnet : 500</li></ol></td><td><ol><li><strong>Source chains supported</strong> : Ethereum, Optimism, BNB Chain, Polygon, Sonic, Mantle, Base, Arbitrum, Avalanche, Linea</li><li><strong>Destination chains supported</strong> : Ethereum, Optimism, Flare, Rootstock, Telos, BNB Chain, Gnosis, Fuse, Polygon, Sonic, Flow, Metis, Core, Glue, Sei, Vana, Story, Gravity, Soneium, Lightlink, Kava, Goat, Abstract, Peaq, Mantle, Kaia, Base, lota, Apechain, Arbitrum, Hemi, Avalanche, Superposition, Ink, Linea, Bera, Codex, Plume, Taiko, Scroll, Degen, Aurora, Rari Chain</li></ol></td></tr><tr><td>Squid Router V2</td><td><ol><li>Mainnet : 600</li></ol></td><td><ol><li><strong>Source chains supported :</strong> Ethereum, Optimism, BNB Chain, Polygon, Fantom, Solana, Bitcoin, Mantle, Base, Arbitrum, Avalanche, Linea, Osmosis, Cosmos Hub</li><li><strong>Destination chains supported</strong> : Ethereum, Optimism, BNB Chain, Polygon, Fantom, Fraxtal, Filecoin, Solana, Moonbeam, Bitcoin, Kava EVM, Mantle, SagaEVM, Base, Immutable zkEVM, Arbitrum, Celo, Avalanche, Linea, Berachain, Blast, Scroll, Osmosis, Noble, DYDX, Neutron, Crescent, Kujira, Umee, Comdex, Juno, Terra, Evmos, Regen, Stargaze, Cosmos Hub, Agoric, Ki, Injective, Fetch, AssetMantle, Carbon, Stride, Archway, Axelar, Impact Hub, Chain4Energy, Chihuahua, Nolus, Persistence, Migaloo, Secret, Sei, Dymension, Nibiru, Celestia, BitSong, Sommelier, Terra Classic, Teritori, Saga, Quicksilver, Desmos, Akash, Mars Hub, Sentinel, LikeCoin, Kava IBC, Decentr, BitCanna, Coreum, Gravity Bridge, Jackal, Cheqd, Lum Network, IRISnet, OmniFlix, Kyve, Lava, Humans.ai, Xion, Elys, Babylon</li></ol></td></tr><tr><td>Aptos Bridge</td><td><ol><li>Mainnet : 700</li></ol></td><td><ol><li><strong>Source chains supported :</strong> Ethereum, Optimism, Binance Smart Chain, Polygon, Aptos, Arbitrum, Avalanche</li><li><strong>Destination chains supported</strong> : Ethereum, Optimism, Binance Smart Chain, Polygon, Aptos, Arbitrum, Avalanche</li></ol></td></tr></tbody></table>


---

# 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.expand.network/ids/bridge-ids.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.