Which USDC should you bridge to Arbitrum?

If your Arbitrum app accepts both, native USDC is usually the cleaner choice; use USDC.e only when the app specifically needs it. The two tokens can share a dollar value, but they are separate tokens with different contract addresses. A bridge route decides which one arrives, so check the destination before sending.

What is the difference between USDC and USDC.e?

Native USDC on Arbitrum is issued by Circle. USDC.e is a bridged token, made when USDC is locked on Ethereum and a corresponding token is issued on Arbitrum. Circle does not issue USDC.e. The “.e” label helps distinguish it, but wallets and apps may show token names differently.

That distinction matters when you deposit into an app, repay a loan or send funds to an exchange. The app may accept one token and reject the other, even if both are called USDC in a wallet. Check the token’s full name and contract address on Arbitrum: native USDC is 0xaf88d065e77c8cC2239327C5EDb3A432268e5831; USDC.e is 0xFF970A61A04b1cA14834A43f5dE4533eBDDB5CC8.

Some guides cover the route and any extra swap steps in more detail; for example, see this biswap guide to stablecoin swaps from Ethereum to Arbitrum. A swap trades one token for another, while a bridge moves tokens between chains. Some routes combine the two.

Which bridge route gives me native USDC?

Use a route that explicitly supports Circle’s Cross-Chain Transfer Protocol, or CCTP, if you want native USDC on Arbitrum. CCTP burns USDC on Ethereum and mints native USDC on the destination chain. It does not create USDC.e by locking the Ethereum tokens and issuing a separate bridged token.

The standard Arbitrum bridge supports USDC transfers, but Arbitrum documents both native USDC and USDC bridged from Ethereum. Don’t assume the word “USDC” in a bridge menu tells you which one you’ll receive. Before signing, check the destination token shown in the route details and compare its address with the app’s accepted token.

What should I check before sending?

Start with the token your destination app accepts. Then check what the bridge route will deliver and what it will cost. The Ethereum transaction needs ETH for gas, and you’ll need some ETH on Arbitrum to pay for later transactions there.

• If the app lists native USDC or the Circle contract address, choose a route that delivers native USDC.
• If it specifically lists USDC.e, confirm the route delivers that token.
• Compare the amount received after fees; a route that combines bridging and swapping can have different costs.
• Send a small test amount first if you’re unsure the app or wallet recognizes the token.

For most transfers, decide based on the destination app, then pick the route that delivers the matching token. The ticker alone is not enough to tell them apart.