Native USDC

USDC issued directly by Circle on a given chain, as distinct from a bridged or wrapped representation such as USDC.e. The two are separate tokens with separate contract addresses and are not interchangeable.

Definition

Native USDC is the version of USDC that the issuer deploys and redeems on that specific chain. A bridged version is a different token: it represents USDC locked somewhere else, issued by a bridge rather than by Circle, and it carries the bridge’s risk on top of the issuer’s.

Why two versions exist

Bridged USDC came first on many networks, because a chain needed a dollar token before the issuer supported it directly. When native issuance arrived later, the bridged token did not disappear, so both circulate side by side with similar names and similar prices.

The ticker in the interface often hides the difference. The contract address never does.

Why it matters in practice

Deposit contracts are specific. A venue that accepts native USDC on a particular network will not credit the bridged variant sent to the same address, and the transaction still succeeds on-chain, which is what makes the mistake expensive.

The two also trade as separate assets. Swapping between them costs a fee and can carry a spread, and a bridged token’s peg depends on the bridge remaining solvent, which is a risk the native token does not have.

How to tell them apart

By contract address, checked against the issuer’s own documentation or the exchange’s deposit screen. Naming conventions vary and are not a reliable signal on their own.

Where you will run into it

At the deposit step of any venue that specifies a token and a network, and when bridging between chains, where the output token is not always the version you expected.