If you have been using a self custody wallet on Base for a while, you may have noticed two tokens that both show up as some version of USDC. One is native USDC, issued directly by Circle. The other is USDbC, short for "USD Base Coin," an older bridged token that predates native USDC on the network. They are not the same contract, and understanding the difference matters if you ever plan to move funds off Base or interact directly with Circle's products.
Why Base ever had two versions of USDC
When Base launched in mid 2023, Circle had not yet issued USDC natively on the network. To give users a dollar stablecoin from day one, Coinbase bridged USDC from Ethereum into Base using the standard Base Bridge. The result was USDbC: a wrapped, IOU style representation of USDC that lived on Base but was backed by USDC locked on Ethereum, not by a direct relationship with Circle.
This is the same mechanism used for any asset moved through a canonical bridge. The original token stays locked on its home chain, and a new token is minted on the destination chain to represent it. It works, but it adds a layer of indirection: the bridged token's value and liquidity depend on the bridge contract and on markets being willing to treat it as equivalent to the real thing.
Circle changed that a few months later. According to Circle's own announcement, native USDC launched on Base on September 5, 2023, issued directly by Circle rather than wrapped through a bridge. From that point on, Base had a stablecoin with the same direct backing and redemption path as USDC on Ethereum, Solana, or any other chain where Circle issues it natively.
How to actually tell them apart
The two tokens often show up with similar tickers and logos in wallet interfaces and token lists, which is exactly how mix ups happen. The only reliable way to tell them apart is the contract address, not the name shown in your wallet.
Based on Circle's published developer documentation, the native USDC contract on Base is:
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
USDbC, the older bridged token, uses a different contract:
0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA
Before sending a meaningful amount of either token anywhere, especially to a centralized exchange or to Circle's own Circle Mint product, check the contract address on a block explorer like Basescan rather than trusting the symbol alone. Circle has specifically warned that USDbC is not issued by Circle and is not compatible with Circle Mint, so sending it there as if it were native USDC can result in funds that are difficult or impossible to recover.
Does it matter which one you hold
For everyday spending and swapping within Base, both tokens have generally traded close to their one dollar peg, and liquidity pools exist that let you move between them. But "close to par" is not the same as "identical," and a few practical differences are worth knowing:
Redemption. Native USDC can be redeemed through Circle's own products under Circle's terms. USDbC cannot, since Circle did not issue it. Its value depends entirely on the Base Bridge continuing to work correctly and on market liquidity for swapping it back into native USDC or into ETH.
Bridge dependency. As a bridged asset, USDbC carries the bridge's risk profile on top of the usual smart contract risk every token carries. That does not mean the Base Bridge is unsafe. It means USDbC has one more layer of contract logic between you and the underlying dollar value than native USDC does.
App support. Over time, more apps, aggregators, and liquidity venues on Base have defaulted to native USDC in their interfaces, since that is what Circle and Coinbase have steered new integrations toward. Older positions, older liquidity pool shares, or tokens received a while back are the most common place USDbC still turns up today.
Migration was never forced. Circle's own messaging described a gradual, optional shift in liquidity from USDbC to native USDC rather than a hard cutover or a deadline. The Base Bridge kept functioning as before. So if you are holding USDbC, nothing automatically happened to it, and nothing will unless you choose to move it.
If you find USDbC in your wallet
There is no urgency here, but there is a reasonable default action for most self custody users: check the contract address to confirm what you are actually holding, then swap it to native USDC if you plan to use the funds with apps, exchanges, or bridges that expect native USDC specifically. As with any swap, check the quoted price and expected output before confirming, since pool depth for a specific pair can vary and is not something a wallet interface guarantees for you.
If you are only swapping within Base and the apps you use already accept both tokens, there is no requirement to convert anything. The main risk to actually avoid is treating USDbC as if it were redeemable through Circle directly, or assuming a wallet's "USDC" label tells you which contract you are dealing with. Verify the address, understand which token you hold, and the rest is a normal swap decision like any other.
This is general information about how a specific token pair works on Base, not financial advice. Always confirm contract addresses and current liquidity directly before moving meaningful amounts of any asset.