USDC.e vs USDC: Bridged vs Native and Why It Matters

Video transcript

Two tokens called USDC circulate side by side on Arbitrum, OP Mainnet and Polygon. They are not the same asset.

Native USDC is issued by Circle and redeemable through Circle Mint. USDC dot e is a copy minted by a third-party bridge.

USDC dot e carries two layers of risk: Circle's, plus the bridge's keys, message checks and upgrade path. Redemption takes an extra step.

A forged bridge message can mint unbacked copies. Our bridge security guide covers five losses valued at more than 1.5 billion dollars at the time.

Circle's Bridged USDC Standard allows an optional upgrade to native. Bridging pauses, minters are removed, roles pass to Circle, locked USDC is burned and the token upgrades.

On November 6, 2026, we read a bridged supply of about 46.3 million on Arbitrum, 18.6 million on OP Mainnet and 1.05 billion on Polygon.

To migrate, check addresses, inventory your USDC dot e, and swap through a deep pool or bridge back and use CCTP. Set a slippage limit and update integrations.

Bridged and omnichain tokens can fail in the wiring. On USDT zero's rollout, Guardian caught a Polygon migration that would have left more USDT zero circulating than USDT backing it.

Read the full article for the address list and migration checklist, or talk to Guardian about verifying every chain your stablecoin reaches.

On Arbitrum, OP Mainnet and Polygon PoS, two tokens called USDC circulate side by side.

When we called symbol() on the bridged contracts on November 6, 2026, each still returned "USDC". Explorers label them USDC.e.

They are not the same asset. The difference decides who can redeem, who can freeze and what can break.

Who Issues Each

Circle's page on bridged USDC is direct: bridged forms "are subject to certain risks and are not issued by Circle."

Circle's USDC Terms, updated October 15, 2026, say Circle "supports only USDC" and is "under no obligation to support any copies of USDC or wrappers."

Redemption needs a Circle Mint account. Holders who cannot open one are not entitled to redeem with Circle.

Tell them apart by address

Symbols mislead, so match the contract address.

Native addresses come from Circle's list, which is the one to check against. The Polygon bridged token's onchain name is "USD Coin (PoS)".

Bridge Risk Inside USDC.e

USDC.e is a claim on a bridge. The bridge holds native USDC on the origin chain and mints a copy on the destination.

Arbitrum's docs describe its USDC.e as Ethereum USDC moved through Arbitrum's canonical bridge, a lock-and-mint flow.

So a USDC.e holder carries two layers of risk:

• Circle's: everything that applies to the USDC locked in the bridge.
• The bridge's: its keys, message checks, configuration and upgrade path.

An attacker who can forge a bridge message can mint copies nothing backs, or release the locked USDC. Either way, the remaining USDC.e is backed by less.

Our bridge security guide covers five bridge losses valued at more than $1.5 billion when they happened.

Freezes and redemption

Circle's blacklist acts on addresses holding native USDC. The bridge's lockbox on the origin chain is one of them.

The USDC.e contract has its own roles, set by whoever deployed it. Read them before you rely on them.

Redemption takes an extra step. Circle redeems only USDC, so USDC.e must first become native USDC, by bridging back or swapping.

The Bridged USDC Standard

Circle's Bridged USDC Standard is its "specification and process for deploying bridged USDC on EVM blockchains," with the option of a later upgrade to native.

The third-party team deploys the bridge and the token, built from Circle's FiatToken code. At first it holds every role: owner, master minter, pauser, rescuer, blacklister and proxy admin.

Circle recommends the name "Bridged USDC (Third-Party Team)" and the symbol USDC.e. The token must not move to a different implementation, other than later FiatToken versions from Circle.

Circle gets "the option, but not the obligation" to take over. If both sides agree, the upgrade runs in five steps:

1. The team pauses bridging and settles in-flight transfers, fixing the bridged supply.
2. It removes every configured minter.
3. It hands the token's roles to Circle through transferUSDCRoles.
4. burnLockedUSDC burns the USDC locked on the origin chain, equal to the bridged supply.
5. Circle upgrades the token to native USDC, keeping its supply, holders and integrations.

The standard "cannot be retroactively applied." It has to be built in before the bridged token is deployed.

Circle says it is available out of the box on Arbitrum Orbit, OP Stack and Polygon CDK chains. It calls Linea's upgrade to native USDC an "industry-first."

Arbitrum, OP Mainnet and Polygon

On these three chains, native USDC arrived as a separate token, and the bridged one stayed in circulation. We read each bridged supply on November 6, 2026.

On Arbitrum, the bridged token "has been renamed to USDC.e," and you choose at deposit time. Arbitrum's bridge gives you USDC.e; Circle's CCTP gives you native USDC.

For OP Mainnet, Circle said explorers would rename the bridged form USDC.e, and Optimism would work with apps on "a smooth transition of liquidity from USDC.e to USDC over time."

For Polygon, Circle said Circle Account would stop USDC.e deposits and withdrawals on November 10, 2023. USDC.e sent there afterwards might not be recoverable, it warned.

Polymarket

Polymarket's docs name pUSD, a Polygon token "backed by USDC," as the collateral for all trading.

Its onramp contract wraps only USDC.e into pUSD, and its offramp unwraps back to USDC.e. Deposits from other chains are wrapped automatically.

How to Migrate Safely

1. Check the address, not the symbol. Match every token against Circle's published native addresses.
2. Inventory your USDC.e. Balances, pool positions, collateral and integrations, chain by chain.
3. Pick a route. Swap through a deep pool on the same chain, or bridge back and move native USDC with CCTP.
4. Set a slippage limit. A swap between the two is a trade, not a conversion.
5. Update integrations. Contract addresses, deposit detection, price feeds and accounting labels.
6. Handle the wrong token. Decide what happens to USDC.e sent to a native USDC deposit address.
7. Watch the roles. Under the standard, track who holds the blacklister, pauser and proxy admin until Circle takes over.
8. Re-verify after an upgrade. Bytecode, implementation and every role, per our multichain verification checklist.

How CCTP moves native USDC

Circle's Cross-Chain Transfer Protocol "natively transfers USDC across blockchains using burn-and-mint." It runs in three steps:

1. You call depositForBurn, which burns USDC on the source chain.
2. After enough block confirmations, Iris, Circle's attestation service, signs the message.
3. The attestation goes to receiveMessage on the destination chain, where USDC is minted.

No lockbox sits in the middle, so no pool of bridged copies builds up. The trust sits with Circle's attester instead.

Circle puts Fast Transfer at about 8 to 20 seconds. Standard Transfer takes 15 to 19 minutes on Ethereum and L2s.

How Guardian Helps

Bridged and omnichain tokens can fail in the wiring even when the code is right.

Guardian's USDT0 case study puts it this way: wired or owned wrongly, "a correct contract becomes an unbacked token or an unrecoverable transfer."

Since February 2025, Guardian has verified every step of USDT0's omnichain rollout. USDT0 uses a different model, LayerZero's OFT standard.

In August 2025, it caught a Polygon migration that would have left more USDT0 circulating than USDT backing it. It was fixed before the transactions ran.

Guardian checks bytecode, roles, peers and every queued transaction for each deployment. See the USDT0 deployment verification case study.

Frequently Asked Questions

Is USDC.e the same as USDC?

No. Both can show the symbol USDC onchain, but USDC.e is a bridged copy backed by USDC locked in a bridge. Circle issues native USDC and says bridged forms are not issued by Circle.

Is USDC.e riskier than USDC?

It carries USDC's risks plus the bridge's: its keys, message checks, configuration and upgrade path. Circle says bridged forms of USDC are subject to certain risks. Redeeming with Circle also takes an extra step.

How do I convert USDC.e to USDC?

Swap it through a liquid pool on the same chain, or bridge it back to its origin chain and move native USDC with CCTP. Check the address of what you receive against Circle's published list.

What is the Bridged USDC Standard?

Circle's specification for third-party bridged USDC on EVM chains. A token built to it can later be upgraded in place to native USDC if Circle and the bridge team agree, after the locked USDC is burned.

Sources

• Circle: Bridged USDC Standard
• Circle: Bridged USDC Standard, stablecoin-evm repository
• Circle: USDC Terms (updated October 15, 2026)
• Circle Developers: USDC contract addresses
• Circle Developers: Cross-Chain Transfer Protocol
• Circle Developers: CCTP technical guide
• Circle Developers: CCTP supported chains and domains
• Arbitrum Docs: USDC on Arbitrum One
• Circle: What you need to know: native USDC on OP Mainnet (August 30, 2023)
• Circle: What you need to know: native USDC on Polygon PoS (September 28, 2023)
• Optimistic Etherscan: USD Coin (Bridged from Ethereum) (USDC.e)
• Polymarket Docs: Polymarket USD (pUSD)
• Guardian: Cross-Chain Bridge Security: How Bridges Get Hacked
• Guardian: Multichain Stablecoin Deployment Verification Checklist
• Guardian: USDT0 Deployment and Configuration Verification case study