English
Supported chains
Supported chains
Twin tokens are deployed across 4 EVM networks. All 10 tokens exist on all 4 networks and can be bridged between any of them.
| Network | Chain ID | LayerZero EID | Explorer | Status |
|---|---|---|---|---|
| Base | 8453 | 30184 | basescan.org | ✅ Active |
| Polygon | 137 | 30109 | polygonscan.com | ✅ Active |
| Arbitrum One | 42161 | 30110 | arbiscan.io | ✅ Active |
| Ethereum | 1 | 30101 | etherscan.io | ✅ Active |
What the LayerZero EID is
The Endpoint ID (EID) is the identifier LayerZero V2 uses to address messages between networks. It is not the same as the EVM chain ID: Twin's bridge uses the EID to route each cross-chain transfer. See Bridge for details.
Public RPCs
Twin reads on-chain state through public RPCs. For integrations, any RPC for the relevant network works:
| Network | Reference public RPC |
|---|---|
| Base | https://base-rpc.publicnode.com |
| Polygon | https://polygon-bor-rpc.publicnode.com |
| Arbitrum | https://arbitrum-one-rpc.publicnode.com |
| Ethereum | https://ethereum-rpc.publicnode.com |
Contract addresses differ per network — the same token has a different address on each chain. See Stablecoin contracts.
Coming soon
Network support grows with the product. New chains and fiat ramps will be documented here as they launch.
Last modified on