USDbC, short for Bridged USDC, is the pre-CCTP version of USDC that Coinbase issued through the Base canonical bridge in August 2023, before Circle launched native USDC on Base in early September 2023. It is not redeemable with Circle. Its peg depends on the Base bridge contract holding ETH-mainnet USDC one-for-one, and its liquidity has been falling steadily as decentralized exchanges, lending markets, and Coinbase itself migrate to native USDC on Base.
​

This article covers what USDbC is, why it exists, how it differs from native USDC on Base, where its liquidity sits in 2026, and the cleanest paths to convert it. The pattern repeats across other chains under names like USDC.e on Avalanche and Polygon, so the lessons here apply broadly.
​

USDbC is a wrapped representation of USDC that lives on the Base network. Each USDbC token is backed one-for-one by USDC sitting in the Base L1 standard bridge contract on Ethereum mainnet. The contract address on Base is 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA, with the symbol USDbC and the same six decimals as native USDC.
​

The "b" prefix is the convention Coinbase chose to disambiguate the bridged token from native USDC, similar to how Circle and chain teams later landed on the ".e" suffix elsewhere. Before native USDC launched on Base in September 2023, USDbC was the only USDC on the network and carried the plain USDC ticker on most explorers. Coinbase later renamed the on-chain token to "USDbC" to avoid confusion with the new native asset.
​

USDbC is governed by the same OpenZeppelin upgradeable proxy pattern used by Coinbase's other Base contracts, and the underlying USDC reserve sits in the Base canonical bridge. There is no Circle attestation, no Circle-controlled minter, and no path to redeem USDbC directly with Circle for a dollar. To exit USDbC for fiat, holders either swap into native USDC and use Circle's path or rely on the canonical bridge to withdraw to mainnet USDC, then off-ramp through a centralized exchange.
​

As of Q1 2026, USDbC supply on Base sits in the low tens of millions, down from a peak of more than $200M in late 2023, according to DeFiLlama's stablecoin dashboards. Native USDC on Base is the dominant USD asset, and Base itself reports more than $4.4B in chain TVL, according to the DeFiLlama chain page for Base.
​

Base launched on August 9, 2023. At launch, Circle had not yet deployed native USDC on Base, and Coinbase needed a USDC that could function inside Base from day one for liquidity, fees, and onboarding. The fastest path was to mint a Base-side representation of mainnet USDC through the chain's canonical bridge. That asset became USDbC.
​

This is the same playbook every L2 used in the pre-CCTP era. When a new chain launched without Circle support, the chain team or its largest exchange partner would deposit mainnet USDC into the canonical bridge and mint a wrapped version on the L2 to seed liquidity. Circle's Cross-Chain Transfer Protocol (CCTP) only entered general availability in April 2023 and at first supported a small set of chains, so for nearly every new EVM rollup the canonical-bridge route was the default.
​

USDbC was therefore a bridge asset by necessity, not by design. The intent from Coinbase was always to retire it once Circle launched native USDC on Base, which happened on September 5, 2023. From that point onward, every dollar of new USDC liquidity on Base has been native USDC, while USDbC supply has only fallen.
​

The asymmetry matters: bridged versions of USDC are mintable on the chain side but only burnable through the chain's bridge withdrawal path. The redemption guarantee of native USDC, where Circle pays out a dollar for each token, does not transfer through the bridge. This is the key risk lens for every "X.e" or "X-bridged" stablecoin on a chain that later gets native issuance.
​

The two assets share a name and a peg target, but the underlying mechanics are different. Treating them as interchangeable is the most common user mistake on Base.
​

Native USDC on Base lives at contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. It is minted and burned by Circle through CCTP and through Circle's Mint API. Coinbase, Stripe, and Robinhood all settle USDC payouts on Base into this contract. Circle's transparency report, Circle Transparency, attests to the dollar reserves backing total USDC supply across chains, and Circle will redeem native USDC for a dollar through its institutional account flow.
​

USDbC at 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA is minted by the Base canonical bridge whenever a user deposits mainnet USDC into the L1 standard bridge. To exit USDbC, a user has to call the bridge withdrawal path, wait the seven-day challenge window typical for optimistic rollups, and receive USDC back on Ethereum mainnet. The seven-day delay is the same finality posture every Optimism-stack chain inherits from Optimism's standard bridge.
​

Three practical differences fall out of that:

The third point is what drives the slow drain in USDbC pool depth: every aggregator that adds Base support builds against native USDC by default, leaving USDbC pools to internal DEX traders and stragglers.
​

USDbC liquidity is concentrated in a small set of DEX pairs on Base. The largest historical home was the USDbC/USDC pool on Aerodrome, which was the canonical migration route during the September 2023 native-USDC launch. As of Q1 2026, the dominant liquidity pairs are:

The structural picture is clear. New liquidity on Base flows to native USDC pools because Uniswap, Aerodrome, Curve, and the Base ecosystem all standardized on the native asset for new pairings. Lending markets like Aave V3 on Base only list native USDC. Morpho Blue's Base markets reference native USDC. Every new yield primitive on Base measures itself in native USDC, which compresses USDbC use cases to legacy positions and migration flows.
​

For a holder, the practical implication is that USDbC is functional but increasingly off the beaten path. Slippage on USDbC pools is small at typical retail size, but enterprise-size trades will see noticeable price impact compared to native-USDC routes. Any time a user holds USDbC, the cleanest read is to migrate first, then transact.
​

There are three reliable routes to convert USDbC into native USDC. Each has a different cost, latency, and trust posture.
​

Aerodrome's USDbC/USDC stable pool is the simplest route. The pool uses the Solidly-style stable curve, which holds the price tightly to 1:1 inside reasonable size. For typical retail amounts, a swap on Aerodrome takes one transaction, costs Base gas (a few cents), and settles instantly. For larger amounts, traders should use an aggregator like Uniswap's auto-router or LI.FI to split between Aerodrome and Uniswap V3 ranges.
​

The trust assumption is the Aerodrome contract plus the underlying USDbC and USDC contracts. No bridge withdrawal is involved.
​

Holders with Coinbase accounts can deposit USDbC, convert to USDC inside the exchange, and withdraw native USDC back to Base. Coinbase's deposit page accepts USDbC explicitly because of its launch role. This route is convenient for users already on Coinbase but adds custody risk for the duration of the round trip.
​

For users who want to consolidate stablecoins across chains, an aggregator like Jumper, LI.FI, or Across can take USDbC on Base in and deliver native USDC on Base, Ethereum, or another supported chain in one click. Internally, these aggregators usually route through Aerodrome or Uniswap on Base before applying any cross-chain transport.
​

For programmatic use cases such as treasury operations or merchant payouts, swap quotes can be fetched from these aggregators' APIs and executed under one signature. Eco handles routing through native USDC on Base via CCTP for orchestration flows, so a wallet holding USDbC should swap to native USDC first before initiating an Eco-orchestrated cross-chain transfer.
​

USDbC is one example of a broader pattern. Whenever a chain launches without native USDC, a bridged variant takes its place. Once Circle deploys native USDC, the bridged version starts a multi-year decline.
​

The naming convention varies. Coinbase chose the "b" prefix for Base. Avalanche, Polygon, Arbitrum, Optimism, and others standardized on the ".e" suffix, which is documented in our deeper write-up on USDC.e. The mechanics are the same in every case:

The migration timeline differs by chain. Arbitrum's USDC.e migration took roughly two years to complete the bulk of the rotation. Polygon's USDC.e is still working through legacy holdings. Base's migration started in September 2023 and is well advanced, but USDbC pools still hold meaningful supply because some long-tail integrations have not retired the old contract.
​

For builders, the takeaway is to default to the native-USDC contract address on every chain and to treat any bridged variant as a migration target rather than a settlement asset. For users, the takeaway is to recognize the bridged variant by its prefix or suffix and to convert it before assuming a position works the way native USDC works.
​

The same pattern applies in reverse direction too. Tether issued USDT0 and similar bridged variants on chains where canonical USDT is not native. Algorithmic stablecoins like Sky's USDS and Ethena's USDe rely on cross-chain wrappers in some deployments. Whenever a stablecoin shows up on a new chain ahead of native issuance, the bridged-variant playbook is in motion. USDbC is the cleanest case study because the migration window is well documented and the resolution path is straightforward.
​

USDbC has not disappeared from Base. It still appears in specific corners of the ecosystem, and recognizing them is useful both for active users and for any builder shipping a Base-side product. The places USDbC remains operational fall into four buckets.
​

Legacy DEX pairs. Aerodrome and Uniswap V3 still maintain USDbC pools because long-tail traders continue to use them, especially as cross-pair entry points for ETH on Base. Aerodrome's veAERO incentive program has steadily dialed down emissions on USDbC pairs, accelerating the rotation toward native USDC pairings.
​

Older NFT and gaming integrations. Some Base apps that launched between August and December 2023 hardcoded USDbC as the payment asset. Migrating those contracts requires a redeploy or an upgrade path, and a meaningful share have not done either yet. Coinbase's OnchainKit documentation now defaults to native USDC, which is shrinking the share of new apps starting on USDbC.
​

Cold wallets and off-chain custody. Long-term holders who acquired USDbC during Base's launch period and have not actively rebalanced still hold the legacy contract. Some custodians supported USDbC for accounting reasons through 2024 and only added native USDC later, leaving residual USDbC in custody balances.
​

Bridge withdrawal queues. Any USDbC moved through the Base canonical bridge withdrawal path resolves on Ethereum mainnet as USDC. The bridge itself does not distinguish, since the asset on mainnet is canonical USDC, but the seven-day finalization window means some volume sits "in flight" at any given time.
​

Base's own developer pages now mark native USDC as the default and document USDbC as a legacy asset, so the structural endpoint is clear. The lingering supply is mostly inertia, not active demand.
​

USDbC is not a high-risk asset by stablecoin standards, but its risk profile is different from native USDC, and any holder should understand the difference.
​

Smart-contract risk on the Base canonical bridge. USDbC's peg depends on the bridge contract continuing to hold one mainnet USDC for every USDbC outstanding. Optimism-stack bridges have a strong audit history, but a successful exploit on the bridge would compromise USDbC backing. Base's contract documentation lists the relevant addresses for monitoring.
​

No Circle redemption. A holder cannot redeem USDbC for fiat through Circle. Every fiat exit path runs through a swap to native USDC first. In an extreme stress scenario, this means USDbC's market price could decouple from $1 even if mainnet USDC remains pegged, because the secondary market depends on Base-side DEX depth.
​

Declining liquidity. As pools migrate to native USDC, slippage on large USDbC trades grows. The trend is structural and one-directional, since no major venue is adding new USDbC liquidity. Treasury teams holding meaningful USDbC positions should plan a migration window rather than assume the same liquidity profile will exist in twelve months.
​

Integration drift. Some older Base apps still expose USDbC pairs, and a user who deposits USDbC into a contract expecting native USDC behavior could get unexpected results. Always check the contract address before connecting a wallet to a Base app.
​

None of these risks make USDbC unsafe for current use. They simply make it the wrong default for new positions. The practical rule for 2026 is: hold native USDC, swap to USDbC only when an integration specifically requires it, and migrate legacy USDbC balances when the gas cost is acceptable.
​

For developers shipping on Base, USDbC creates a small but real set of edge cases. These are the points worth checking before deployment.

None of these steps require heavy engineering. They are mostly hygiene around the contract address and the balance display. Skipping them is what produces the long-tail of "I sent USDC but my dApp didn't recognize it" support tickets that still surface on Base in 2026.
​

Eco is a stablecoin orchestration network that moves USDC, USDT, and other stablecoins across 15 supported chains, including Base. Eco's routing layer settles in native USDC on every chain that supports it, because Circle CCTP only operates on the native asset and because aggregator pricing is best on the native pair.
​

For a developer integrating Eco's SDK or API, the practical effect is that any USDbC sitting in a wallet has to be swapped before initiating a cross-chain Eco route. This is a one-line action through Aerodrome or an aggregator and only applies to legacy holdings. New deposits to a wallet from Coinbase, Robinhood, or any modern fiat on-ramp arrive as native USDC by default.
​

For a treasury team, Eco's automation surface assumes native USDC. Programmable addresses, sweep automation, and conditional payouts all operate against the native contract. Migrating USDbC to native USDC ahead of an Eco integration removes a source of operational friction and makes the resulting flows simpler to audit.
​

No. USDbC is the bridged version of USDC issued through the Base canonical bridge. Native USDC on Base is issued directly by Circle and lives at a different contract address. They share a peg target but have different mint, burn, and redemption paths.
​

No. Circle only redeems native USDC. To convert USDbC to fiat, swap it for native USDC on Base through Aerodrome or Coinbase, then redeem the native USDC through Circle's institutional flow or off-ramp through an exchange.
​

Aggregators, lending markets, and Coinbase all migrated to native USDC after Circle's September 2023 launch on Base. New USDC liquidity on Base flows to the native contract, leaving USDbC pools to legacy traders. The trend is structural and one-directional.
​

Check the contract address. USDbC sits at 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA on Base. Native USDC sits at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Most modern wallets label them USDbC and USDC respectively, but contract address is the only reliable check.
​

For typical retail amounts, the Aerodrome USDbC/USDC stable pool is the cheapest route. It costs Base gas plus a small swap fee and settles in one transaction. Larger trades should split across Aerodrome and Uniswap V3 through an aggregator like LI.FI or Jumper to reduce slippage.
​

There is no public deprecation date. Coinbase has not announced a sunset for the USDbC contract, and the Base canonical bridge will continue to back it as long as deposited USDC remains in the L1 contract. The practical outcome is gradual rather than abrupt: liquidity, integrations, and supply will continue to fall as the ecosystem standardizes on native USDC.
​