USDC.e is bridged USD Coin: a token contract minted by a chain's canonical bridge that represents USDC locked on Ethereum, rather than USDC issued natively by Circle on the destination chain. The ".e" suffix marks the asset as the bridge-wrapped version, separate from the native USDC contract Circle later deploys directly. You will see USDC.e on chains where Circle launched native USDC after the chain already had a working bridge, including Avalanche, Polygon, Arbitrum, Optimism, and Linea.
​

For most users, USDC.e and native USDC trade close to 1:1 because deep liquidity pools on Curve and Uniswap arbitrage any drift. The two are not the same asset, though. USDC.e cannot be redeemed for dollars at Circle. It depends on the bridge contract that minted it, and its long-term liquidity tracks how aggressively Circle and the chain's foundation push the migration to native USDC. This article walks through what USDC.e is, why it exists, where you will find it, the risks of holding it, and how to swap it back into a native asset Circle directly redeems.
​

USDC.e is a wrapped, bridged version of USDC. When a non-Ethereum chain launches and wants USDC liquidity before Circle issues a native version, the chain (or its canonical bridge operator) deploys a bridge that locks USDC on Ethereum and mints a representation token on the new chain. That representation is the asset users see in their wallets as USDC.e on Avalanche, USDC.e on Polygon, USDC.e on Arbitrum, and so on. The naming convention with the trailing ".e" is the chain's way of signaling that the token is bridged, not natively issued by Circle.
​

The mechanism is straightforward. A user deposits USDC into the canonical bridge on Ethereum. The bridge locks those tokens in a contract and emits a message to the destination chain. A bridge module on the destination chain mints an equivalent amount of USDC.e to the user's address. To withdraw, the user burns USDC.e on the destination chain, which unlocks the underlying USDC on Ethereum. The supply of USDC.e on each chain is therefore backed 1:1 by USDC sitting in the bridge's lockbox on Ethereum, not by Circle reserves directly.
​

Native USDC works differently. Circle deploys its own USDC contract on the destination chain, mints supply against fiat reserves it holds at custodian banks, and accepts redemptions from the chain back to dollars through Circle Mint. There is no bridge in the path. A native USDC token on Avalanche is a direct claim on Circle's reserves, the same way native USDC on Ethereum is. A USDC.e token on Avalanche is a claim on USDC locked at the Avalanche bridge.
​

This distinction matters for redemption, smart-contract risk, and DEX liquidity. A user holding native USDC can move directly through Circle's Cross-Chain Transfer Protocol (CCTP), which burns native USDC on the source chain and mints native USDC on the destination, with no wrapped intermediary. A user holding USDC.e cannot use CCTP. They have to swap to native USDC first, then use CCTP, or unwind through the original bridge.
​

USDC.e exists because chains needed dollar liquidity before Circle was ready to issue USDC natively. Circle launches native USDC on a chain after that chain demonstrates traction, after legal and operational reviews complete, and after Circle's mint and redeem rails are integrated with custodians. That process takes time. Avalanche launched its C-Chain in 2020 and gained meaningful TVL through 2021. Circle's native USDC on Avalanche did not arrive until June 2023, roughly two years later.
​

During that gap, the only way to use USDC on Avalanche was to bridge it. Avalanche's official bridge, the Avalanche Bridge, handled deposits and minted USDC.e. The same pattern played out on every chain that launched before Circle's native deployment: Polygon's PoS bridge minted USDC.e on Polygon, Arbitrum's canonical bridge minted USDC.e on Arbitrum, Optimism's standard bridge minted USDC.e on Optimism. By the time Circle was ready to launch native USDC, the bridged version already had billions in supply, deep DEX liquidity, and integrations across lending markets and aggregators.
​

Once native USDC arrives, Circle and the chain's foundation typically encourage a migration. Native USDC redeems directly to dollars, qualifies for CCTP, and avoids the bridge as a single point of failure. Most ecosystems run a migration period where USDC.e and native USDC coexist, then liquidity gradually shifts toward native through DEX incentives and integrator updates. The legacy USDC.e token continues to exist, but it stops being the default. New listings, new lending markets, and new payment integrations reference native USDC. USDC.e becomes the token holders convert away from, not the one they accumulate.
​

The other reason USDC.e persists is composability. Hundreds of DeFi positions across Aave, Curve, Uniswap, and other protocols on each chain were originally denominated in USDC.e. Migrating those positions takes time and, in some cases, requires unwinding leveraged loops or re-pairing liquidity. As long as those legacy positions exist, USDC.e holds residual liquidity and stays in circulation.
​

USDC.e and native USDC look interchangeable to a casual user. Both target a $1 peg. Both have ticker symbols that include "USDC". Both show up in wallets and DEX swap interfaces. The differences are in the contract, the issuer, and the redemption path.
​

The contract addresses are different. On Avalanche, USDC.e lives at 0xA7D7079b0FEaD91F3e65f86E8915Cb59c1a4C664. Native USDC lives at 0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E. A wallet sees these as two separate tokens. Sending USDC.e to a contract that expects native USDC will fail or land in a token-mismatched state.
​

The issuer is different. Circle issues native USDC and publishes monthly reserve attestation reports covering the cash and short-dated Treasury holdings backing supply. USDC.e is not issued by Circle. The bridge contract issues it, and the backing is the USDC locked at the bridge's lockbox address on Ethereum. If the bridge contract were exploited or its message-passing layer compromised, the USDC.e supply on the destination chain could become detached from its backing.
​

The redemption path is different. A holder of native USDC on Avalanche can move it to native USDC on Ethereum via CCTP and redeem at Circle for dollars. A holder of USDC.e on Avalanche has to bridge back through the Avalanche Bridge to recover Ethereum USDC, which then redeems at Circle. The extra step adds bridge withdrawal time (often hours, occasionally longer if the bridge is congested) and exposes the user to the bridge's smart-contract surface for the duration of the withdrawal.
​

For most onchain trading, the practical difference is liquidity. As migrations progress, native USDC accumulates the deepest DEX pools, and USDC.e pools start to thin out. Curve maintains dedicated USDC.e/USDC pools on most affected chains specifically so holders can swap with low slippage. Aggregators like 1inch and Paraswap route through these pools when users initiate a swap.
​

Each chain ran its own migration timeline, and the details affect which tokens are dominant today. The breakdown below covers the chains where USDC.e is most visible.
​

Avalanche has both USDC.e (the bridged version from the Avalanche Bridge) and native USDC. Circle launched native USDC on Avalanche on June 29, 2023. The native contract is at 0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E and supports CCTP. Circle has since coordinated with the Avalanche Foundation to migrate liquidity, and as native USDC supply has grown, USDC.e has receded as a default. Major DEX aggregators on Avalanche default to native USDC when routing.
​

Polygon's situation is more layered because of the chain's bridge architecture. The original USDC on Polygon was bridged via the Polygon PoS bridge and is sometimes labeled USDC.e on explorers and aggregators. Circle launched native USDC on Polygon PoS on November 10, 2023. After that, Circle and Polygon Labs ran a migration program, and in 2024 the bridged USDC was rebranded in some interfaces from "USDC" to "USDC.e" to distinguish it from the native version. Native USDC on Polygon PoS supports CCTP.
​

Arbitrum had USDC.e (originally just "USDC" in many wallets) as the bridged token from the Arbitrum native bridge. Circle launched native USDC on Arbitrum One on June 8, 2023. The two tokens coexisted, and over the following year native USDC took over as the default for new DEX pools, lending markets, and integrations. Native USDC on Arbitrum supports CCTP.
​

Optimism follows the same pattern. The Optimism standard bridge minted USDC.e (originally labeled "USDC"). Circle launched native USDC on Optimism on September 21, 2023. The transition involved relabeling the bridged token from "USDC" to "USDC.e" on block explorers and many wallets, then migrating liquidity to the native contract. Native USDC on Optimism supports CCTP.
​

Linea launched in mid-2023 and used a bridged USDC token by default. Circle has since shipped native USDC on Linea, and the legacy bridged token is treated as USDC.e. Linea's bridge architecture relies on the canonical Linea bridge for the wrapped version, with native USDC supporting CCTP for direct cross-chain moves.
​

Base is the exception. When Base launched in August 2023, the canonical bridge minted a bridged USDC variant called USDbC (USD Base Coin), not USDC.e. The contract is at 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA. Circle launched native USDC on Base on September 5, 2023, only weeks after the chain's mainnet. USDbC and USDC.e are functionally the same idea — a bridged representation of Ethereum USDC — they just use different naming. USDbC is being deprecated in favor of native USDC, and Coinbase's wallet and exchange integrations have largely migrated. Native USDC on Base supports CCTP.
​

For holders sitting on USDC.e, conversion to native USDC is straightforward. There are three common paths, each with different tradeoffs.
​

Path 1: DEX swap on the same chain. The fastest option is swapping USDC.e for native USDC on a DEX. Curve runs dedicated USDC.e/USDC pools on Avalanche, Polygon, Arbitrum, and Optimism specifically for this purpose, and the slippage on small-to-mid swaps is usually a few basis points. Aggregators including 1inch, Uniswap, and Paraswap will route through Curve automatically. For amounts above six figures, splitting across multiple pools or using an OTC desk avoids price impact.
​

Path 2: Circle's official migration tool. Circle has, on selected chains, offered a 1:1 migration tool that lets institutional holders swap USDC.e for native USDC at no fee. Availability varies by chain and program window. The migration tool typically runs through Circle Mint and requires a Circle account. For retail amounts, this is usually slower and more friction than a DEX swap.
​

Path 3: Bridge withdrawal then re-deposit. The original mechanism: withdraw USDC.e back to Ethereum USDC via the canonical bridge, then move that USDC to the destination chain as native USDC via Circle's CCTP. This is the cleanest path for users who do not want to trust DEX liquidity, but it takes longer (bridge withdrawal windows can be hours) and incurs gas on three transactions.
​

For most users on most chains, Path 1 — a DEX swap routed through Curve — is the right choice. It takes one transaction, settles in seconds, and the slippage is typically lower than the gas saved on avoiding a bridge round-trip.
​

USDC.e is generally considered a safe asset, but it carries categories of risk that native USDC does not. Holders should understand each before holding meaningful balances long-term.
​

Smart-contract risk on the bridge. USDC.e supply is backed by USDC locked at the canonical bridge contract on Ethereum. If that contract is exploited — whether through a vulnerability in the contract itself or in the cross-chain message-passing layer — the backing could be drained while USDC.e supply continues to circulate. Cross-chain bridges have been a target. The 2022 Ronin Network exploit lost $625 million through a validator key compromise. The 2022 Wormhole exploit lost $325 million through a contract vulnerability. Canonical bridges on production L2s have not had comparable exploits, but the surface exists.
​

No Circle redemption. Native USDC can be redeemed at Circle for dollars 1:1. USDC.e cannot. To convert USDC.e back to dollars, a holder has to first unwind to native USDC (DEX swap, bridge withdrawal, or migration tool), then redeem. Each extra step adds cost and time, and during a stress event, the bridge step could be slow or temporarily unavailable.
​

Liquidity decay over time. As migrations progress, the deepest DEX pools move to native USDC. USDC.e pools shrink. New protocol launches list native USDC, not USDC.e. The result is that USDC.e becomes harder to swap at scale over time, and the price can drift slightly off peg during liquidity-thin periods. Curve's dedicated pools mitigate this, but the long-term direction is clear: the migration tool, not the legacy token, gets the integration support.
​

Delisting risk. Some platforms have started removing USDC.e from listings and routing defaults. Centralized exchanges may treat USDC.e and native USDC as different deposit tokens, with one accepted and the other not. Aggregators and lending markets gradually deprecate USDC.e collateral types. A holder who waits too long to convert may end up needing the bridge withdrawal path because no DEX route exists at depth.
​

Pricing drift. Outside the major Curve pools, USDC.e can trade at a slight discount to native USDC. The arbitrage that holds the peg requires a willing counterparty and active liquidity. Most of the time the spread is one or two basis points. During fast moves, it can widen briefly. For payments use cases where exact 1:1 matters, this drift is a reason to convert sooner rather than later.
​

Despite the migration push, USDC.e still has meaningful liquidity on every chain where it was once the default. The pools concentrate on a handful of venues.
​

Curve runs dedicated USDC.e/USDC stableswap pools on Avalanche, Polygon PoS, Arbitrum, and Optimism. These pools are the primary mechanism by which the USDC.e/USDC peg holds. On Curve, swap fees are typically 1 to 4 basis points and slippage on a $100,000 swap is usually under 5 basis points. The pools have been incentivized by Curve's CRV emissions and by chain-foundation rewards during migration windows.
​

Uniswap V3 hosts USDC.e/USDC concentrated-liquidity pools on the same chains. Liquidity is thinner than Curve for stableswap routing but available, and aggregators route to whichever pool offers the better fill.
​

Centralized exchanges have varied policies. Coinbase deposits and withdrawals on chains with both USDC.e and native USDC default to native; USDC.e deposits may be credited at a delay or rejected. Binance and other major venues treat the two as separate ticker symbols on chains where they distinguish.
​

Lending markets are migrating. Aave and Compound have phased out USDC.e collateral on chains where native USDC is supported, often by reducing borrow caps and incentive emissions on the legacy market and ramping the native version. Holders earning yield on USDC.e in those markets should monitor the migration timeline for their position.
​

The naming pattern across chains is not perfectly uniform. Three labels show up.
​

USDC.e — the most common label. The ".e" is sometimes interpreted as "Ethereum-bridged" or just as a generic suffix marking the asset as bridged. Used on Avalanche, Polygon (post-2024 rebrand), Arbitrum, Optimism, Linea, and most other chains where Circle launched native USDC after a bridged version was already established.
​

USDbC — the Base-specific label. Stands for "USD Base Coin." Functionally identical to USDC.e in concept but named differently because Base launched as a Coinbase-affiliated chain and Coinbase chose its own convention. Now being deprecated in favor of native USDC on Base.
​

USDC (the bare ticker on a chain that has both bridged and native) — historically, the bridged version on Polygon, Arbitrum, and Optimism was simply called "USDC" with no suffix because it was the only USDC available. After Circle launched native USDC, wallets and explorers retroactively relabeled the bridged token as USDC.e. A user holding "USDC" on Arbitrum from 2022 may have had their wallet display change to "USDC.e" without their balance changing — same token, new label.
​

For new users coming to a chain today, the rule is simple: if a token has any suffix or prefix beyond plain "USDC", it is bridged. Native USDC always uses the unmodified ticker. If two tokens both appear with similar names, check the contract address against Circle's official multi-chain USDC list — that is the canonical source for the native contract on each supported chain.
​

For builders moving stablecoins across chains, the existence of USDC.e changes how routing works in practice. A user holding USDC.e on Avalanche cannot use CCTP directly — CCTP only works with native USDC. To move funds from Avalanche to, say, Base, the user has to first swap USDC.e to native USDC on Avalanche, then route through CCTP, then arrive in native USDC on Base. That is two onchain steps minimum, plus the CCTP attestation wait.
​

Eco Routes (the developer-facing CLI and API for stablecoin orchestration) handles the swap-then-route step automatically when a user input wallet contains USDC.e on a chain that has native USDC. The router converts at the best available rate (typically through Curve), then executes the cross-chain leg via CCTP, Hyperlane, or LayerZero depending on which path optimizes cost and finality. From the user's perspective, the input is "USDC on Avalanche to USDC on Base" and the routing layer figures out that USDC.e is involved. For developers integrating Eco's API, the recommendation is to detect USDC.e balances at the wallet layer, surface a "swap to native USDC for best rates" hint to the user, and let Eco handle the routing once the wallet is in a native-USDC state.
​

Across the broader ecosystem, the trend is clear: native USDC is the default for new builds, and the orchestration layer (whether Eco Routes, LI.FI, or another router) is responsible for translating between legacy bridged versions and native versions. USDC.e is not going away tomorrow — Avalanche still has hundreds of millions in USDC.e supply, and Polygon's bridged USDC.e is still measured in nine figures — but the path of least resistance points to native, and most product surfaces are already there.
​

No. USDC.e is a bridged version of USDC, minted by a chain's canonical bridge against USDC locked on Ethereum. Native USDC is issued directly by Circle on the destination chain and redeems 1:1 to dollars. The two tokens have different contract addresses and different backing models.
​

Not directly. To redeem, a holder has to first convert USDC.e to native USDC (via a Curve swap, an aggregator, or a bridge withdrawal), then redeem the native USDC at Circle Mint. The extra step adds time and cost compared to redeeming native USDC directly.
​

USDbC is the Base-specific label for bridged USDC. USDC.e is the same concept on Avalanche, Polygon, Arbitrum, Optimism, and Linea. Both are bridged representations of Ethereum USDC, and both are being phased out in favor of native USDC issued by Circle directly on each chain.
​

If a wallet shows USDC.e, the funds were either bridged to the chain through its canonical bridge before native USDC existed, or the wallet automatically labels the legacy bridged token as USDC.e. Many wallets retroactively relabeled "USDC" to "USDC.e" on Polygon, Arbitrum, and Optimism after Circle deployed native USDC on those chains.
​

Some platforms have already started phasing out USDC.e support, and the trend is toward gradual deprecation. Curve maintains USDC.e/USDC swap pools so holders can convert with low slippage, but DEX listings, lending markets, and exchanges increasingly default to native USDC. Holders should plan to convert rather than hold long-term.
​