Skip to main content
A route is one direction, one provider and one asset pair. Ask GET /v1/routes for the live list: each row carries its CAIP IDs, minimum and maximum, funding modes, available flag and typical time.

​
CCTP chains

USDC deposits and withdrawals work on every CCTP EVM chain with native USDC: Arbitrum, Arc, Avalanche, Base, Codex, Cronos, EDGE, Ethereum, HyperEVM, Ink, Linea, Monad, Morph, OP, Pharos, Plasma, Plume, Polygon PoS, Sei, Sonic, Unichain, World Chain, X Layer and XDC. Circle’s TokenMessengerV2 has the same address on every EVM mainnet, so one adapter serves all of them.

​
USDT0 chains

USDT deposits and withdrawals use USDT0 on its native chains, including Ethereum, Arbitrum, Polygon, OP, Unichain, Ink, Monad, Sei, HyperEVM, Mantle, Plasma, Berachain, Morph and X Layer. On Stellar, USDT0 is converted to and from USDC on the Stellar DEX.
USDT0 withdrawals to Ethereum are refused. The LayerZero fee from Stellar to Ethereum is above the per-transfer fee cap.

​
Funding modes for deposits

On a chain that is not sponsored, the app shows a warning on the deposit address. Funds sent there cannot be moved by the app and need a manual recovery.

​
Not supported

Solana, Starknet, Sui and Aptos through CCTP (each needs its own adapter), and BNB Chain through CCTP.

​
Chain identifiers

Chains use CAIP-2 (eip155:8453, stellar:pubnet). Assets use CAIP-19 on EVM chains and stellar:CODE:ISSUER on Stellar. Route rows are generated from the SDK’s chain registry. Enabling a chain is a new registry row and a mainnet canary; it needs no code change.