Arbitrum One has two different USDC assets. Native USDC is issued by Circle; USDC.e represents USDC bridged from Ethereum and is not issued by Circle. Choosing Arbitrum One as the destination network therefore leaves a second question unresolved: which token will arrive?
| What you need to know |
|---|
| Native USDC and bridged USDC.e both exist on Arbitrum One. |
| The two assets have different token contract addresses. |
| Circle issues native USDC, while USDC.e is a bridged form from Ethereum. |
| The documented bridge routes can deliver different receiving assets. |
This distinction dates to Circle’s native Arbitrum launch in 2023. It is an existing network feature, rather than a new launch. The comparison below uses Circle’s issuer information and Arbitrum’s bridge documentation, checked on 23 October 2026.
The network stays the same; the contract changes
Circle’s native-USDC announcement identifies the Arbitrum One contract as 0xaf88d065e77c8cC2239327C5EDb3A432268e5831. For bridged USDC.e, it lists 0xff970a61a04b1ca14834a43f5de4533ebddb5cc8. Arbitrum’s documentation lists the same pair. These are token contract addresses used to identify the assets, rather than payment destinations supplied by a recipient.
Both addresses belong to the same network, so the distinction survives a correct network selection. A reader comparing two balances labelled with a similar dollar symbol is comparing separate tokens if those balances refer to these different contracts. The issuer description and the contract address answer different parts of the question: who issues the asset, and which onchain token the balance represents.
The label USDC.e does not mean Circle issued a second native version on Arbitrum One. Circle explicitly distinguishes it from its native issuance. This comparison also does not establish that a particular exchange accepts either asset; a service’s deposit instructions are a separate source of evidence.
One starting asset, two documented outputs
The Arbitrum bridge explanation describes two routes for USDC starting on Ethereum. The canonical lock-and-mint route can deliver bridged USDC.e. Circle’s Cross-Chain Transfer Protocol can deliver native USDC through a mint-and-burn mechanism.
For the same Ethereum starting asset and the same Arbitrum One destination, those routes lead to different token contracts. The receiving asset is therefore part of the transfer’s terms, alongside its destination network. Calling both operations a USDC bridge transfer leaves out the detail that determines which balance appears at the other end.
That makes the destination token contract a useful point of comparison before approving a route. Matching it to the intended asset resolves the native-versus-bridged question; it does not establish a route’s security, fees or a receiving service’s support. Neither the common USDC name nor the shared network makes the two assets interchangeable for every application.
