Receive native USDC when bridging unless the app you plan to use specifically requires bridged USDC. The right destination token is the one your exchange deposit or protocol accepts.
- Native USDC: Circle-issued and usually the easier choice for deposits and later use.
- Bridged USDC (USDC.e): Useful when a particular pool requires that contract.
- Before bridging: Match the destination contract address, not just the “USDC” ticker.
Which USDC Will Your Destination Accept?
Native USDC is the right choice when the receiving exchange or app lists Circle’s token contract. In Jumper bridge, compare the destination token on each route before comparing quoted amounts.
An exchange may offer a deposit labelled “USDC on Arbitrum” yet credit only the contract shown in its deposit instructions. Copy that address and compare it with the address in the route’s destination token selector. A matching ticker or logo cannot confirm that the tokens are interchangeable. Sending USDC.e where the exchange expects native USDC may leave the deposit uncredited.
Arbitrum’s USDC documentation shows the distinction: native USDC uses 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, while bridged USDC.e uses 0xff970a61a04b1ca14834a43f5de4533ebddb5cc8. On Optimism, native USDC and USDC.e also have different contracts. Apply the same address check on Base and Polygon, where a familiar USDC name may likewise appear beside another version. For a protocol, match the address in the pool or deposit screen to the token you will receive.
Which Route Has the Better Risk and Total Cost?
Native USDC usually wins when you account for the token’s backing and what it may cost to use the proceeds.
Which Token Adds Bridge Risk?
Bridged USDC adds reliance on the bridge that locked the original token and issued its wrapped version. Native USDC is issued by Circle and carries Circle issuer risk without that additional wrapping contract. Circle’s CCTP documentation describes the alternative transfer mechanism: CCTP burns USDC on the source chain and mints native USDC on the destination. Native USDC can be redeemed through Circle’s supported channels; a wrapped token first depends on its bridge backing.
Will a Higher Quote Still Be Better Later?
USDC.e can sometimes produce a slightly higher arrival quote because route prices depend on available liquidity and fees. If your next step requires native USDC, converting USDC.e adds a swap, its fee and any price difference. Compare the amount of usable USDC after that conversion. In Jumper bridge, a higher USDC.e quote is worthwhile only when it still serves your intended destination better.
When Does Each Option Win?
- Choose native USDC for an exchange deposit or app that lists the native contract, and when you have no specific use for USDC.e.
- Choose USDC.e for a pool that explicitly requires its contract, after confirming that the quoted route delivers that exact token.