Native vs Bridged Stablecoins: Why Your Chain Has Two USDCs

Open a token picker on Arbitrum, search USDC, and you may get two results. One is USDC. The other is USDC.e. Same six-letter promise, nearly the same price, and most of the time you can hold either without ever noticing the difference.

The rest of the time it matters quite a lot. One of those tokens was issued on that chain by Circle. The other is a claim minted by a bridge, backed by real USDC sitting in a contract on Ethereum. Both are dollars right up until someone questions the thing standing behind them.

Where the second USDC came from

For years, the only way to get USDC onto a new L2 was to bridge it. The bridge locked USDC on Ethereum and minted a representation on the destination chain. That representation was the chain's dollar — pools were built on it, lending markets priced in it, everyone's balance was denominated in it. It just happened to be an IOU rather than the thing itself.

Then Circle started issuing natively on those chains. Suddenly two dollars existed side by side, both called USDC, and the bridged one was renamed with a .e suffix to stop people mixing them up. Native issuance also brought burn-and-mint transfers between chains, which means moving native USDC doesn't leave a pile of collateral sitting in a bridge contract at all.

Why the distinction earns its keep

• Risk stacks. Holding a bridged stablecoin means holding issuer risk and bridge risk. Native is one of those, not two.
• Liquidity splits. Two tokens where there should be one means two sets of pools, and the deeper one isn't always the one you'd assume. Pick wrong at size and you pay for it in price impact.
• They can trade apart. Under stress, bridged versions have traded at a discount to native even when the issuer was entirely fine. The market prices the bridge separately, because it is a separate thing.
• Protocols are picky. A lending market or vault may accept one and not the other, which is a frustrating discovery to make after you've already arrived.

For a $200 pass-through swap, none of this will ruin your week. It becomes real at size, during stress, and any time you're planning to actually hold the position rather than route through it.

What a depeg does to a swap

A depeg isn't an abstraction — it's a specific mechanical thing that happens to your trade, and it's worth having seen it once before it happens to you.

In March 2023, USDC traded down to roughly $0.87 after news about one of the banks holding its reserves. DAI followed it down, because a large share of DAI's backing at the time was USDC. For most of that weekend, stablecoin swaps quietly stopped working: anyone with a normal tight slippage setting watched trades revert over and over, and anyone who "fixed" it by widening tolerance sold dollars at eighty-something cents.

The mechanics are worth understanding. Stable pools are engineered to be almost flat near parity — that's why a stablecoin swap normally costs a rounding error. Push the price outside that narrow band and the curve steepens sharply, so price impact goes from negligible to brutal in a short distance. At the same time the pool goes one-sided, because everyone is selling the same leg. The deep market you were counting on is deep in the wrong direction.

Not every dollar is the same kind of dollar

"Stablecoin" describes a target price, not a design. Four quite different bets currently share the label:

• Fiat-backed — USDC, USDT, FDUSD. Reserves sit off-chain and redemption runs through the issuer, so the risk is custody, banking, and regulation. Depegs here are usually a question about reserves, and usually resolve if the reserves are real.
• Crypto-collateralized — DAI and its descendants. Backed by onchain collateral, overcollateralized, peg held by mechanism. It inherits whatever it's collateralized by, which has at times included large amounts of other stablecoins.
• Synthetic and delta-neutral — USDe and similar. A dollar of value produced by a hedged position rather than a dollar in a bank. Often yield-bearing, frequently well-designed, and a genuinely different risk model: funding rates, venue counterparties, and the liquidity of the hedge itself.
• Yield-bearing wrappers — sDAI, sUSDe, assorted vault receipts. These aren't stablecoins at all. They're deposit receipts whose price drifts upward by design, and a swap treats them as their own asset with their own liquidity.

There's a fifth category — uncollateralized algorithmic dollars — that produced UST and mostly left the field afterward. Its absence from serious usage is not an accident.

Two tokens can both promise a dollar and be entirely different bets. That's fine, as long as you're the one who chose which bet you're making.

A routine that costs you nothing

1. 1Prefer native issuance on the chain you're landing on, especially if you'll hold or deploy rather than immediately move on. Confirm by name and contract, not by symbol.
2. 2Know which pool your depth is in. If you already hold a bridged variant, the liquidity you're relying on may be the native pool — or may not be.
3. 3Keep slippage genuinely tight on stable pairs. A few basis points is normal; treat a revert as a signal rather than a setting to override. Our guide to reading a swap quote covers where that number lives.
4. 4Let the route deliver the asset you actually want, rather than bridging first and fixing it on the far side — that's the whole point of a cross-chain swap.

SwapRoute's token picker is chain-aware and searchable by contract address, with hand-curated entries for major assets on top of the generated registry — so you can confirm which dollar you're selecting before you route into it. Routes are then compared on net output, which means if the deeper market on that chain happens to be the bridged pool, the number will tell you rather than hide it.