How to tell native USDC from bridged USDC

Native USDC is the token Circle issues on a particular blockchain. Circle will redeem only the token implemented at the contract address it publishes for that chain. Bridged USDC is a token minted by a separate protocol after locking Circle’s native USDC on another chain; Circle does not redeem bridged tokens.

Circle publishes the official USDC contract address for each supported network. The only reliable test is an exact, character-for-character match between the contract string shown in a block explorer or wallet and the address on Circle’s contract-address page. Wallet labels, tickers, logos or verified badges do not prove a token is Circle-issued.

The two instruments differ by issuer and redemption rights. Native USDC is issued by Circle on the named chain and is eligible for redemption at Circle. Bridged USDC is issued by the bridge operator; its value depends on the reserves and controls of that bridge, not on Circle’s redemption program.

Circle’s Cross-Chain Transfer Protocol moves native USDC using a burn-and-mint process: tokens are removed on the source chain and new native USDC is created on the destination chain. Lock-and-mint bridges retain the original tokens in a lock contract and mint a separate representation on the destination chain. Those representations remain under the bridge operator’s control.

Operational controls used by institutions and services should require the chain name and the exact Circle contract address for any accepted USDC. If an inbound token’s contract string matches Circle’s published address exactly, it can be treated as native USDC under existing receive rules. If the contract strings do not match, the inbound token should be quarantined and must not be booked as dollars until it is unwrapped or swapped into Circle’s native contract.

Native-USDC failure modes include issuer action, a Circle freeze on the contract, or termination of the issuer-chain relationship. Bridged tokens face bridge-specific risks such as exploits of lock contracts, operator failure or mismanagement. Circle’s blacklist and freeze powers apply only to its native contract; wrappers are subject to the bridge operator’s controls, if any.

To verify holdings, open Circle’s USDC contract-address page, copy the entry for the named chain and compare the exact contract string to the token page in a block explorer or wallet. Do not accept a match based on ticker, logo or wallet label alone.