ArcaniumSupported chains
Every route below moves native USDC in both directions, to and from Arc.
| Chain | Chain ID | CCTP domain |
|---|---|---|
| Arc | 5042 | 26 |
| Ethereum | 1 | 0 |
| Base | 8453 | 6 |
| Arbitrum | 42161 | 3 |
| OP Mainnet | 10 | 2 |
| Polygon | 137 | 7 |
| Avalanche | 43114 | 1 |
| Unichain | 130 | 10 |
| Linea | 59144 | 11 |
| Sonic | 146 | 13 |
| World Chain | 480 | 14 |
| Sei | 1329 | 16 |
The CCTP domain is Circle's own identifier and is unrelated to the EIP-155 chain ID. Integrators need the domain, not the chain ID, when constructing a transfer.
What is deliberately missing
BNB Smart Chain. CCTP lists a domain for it, but Circle does not issue native USDC there — the common BNB “USDC” is a Binance-pegged bridged asset, which is a different thing and not what this moves. Listing it would offer a route that cannot work.
Solana. CCTP supports it, but it is not an EVM chain, so it needs a different wallet connection and transaction format rather than another row in this table. It is a real piece of work, not an oversight.
Arriving with no gas
Bridging into Arc does not require you to already hold Arc gas: Arcanium relays that claim, which is what makes Arc reachable for somebody who has never held anything on it. On Arc, USDC is the gas token — see Getting USDC on Arc — so once the transfer lands you can trade immediately.
Going the other way, you sign the claim yourself. That is not a limitation so much as the ordinary case: you are arriving on a chain you already use and already hold gas on. The mint is permissionless and always pays the recipient written into the message, so claiming it yourself is exactly as safe and cannot be redirected by anyone.