When people talk about "Bitcoin on Ethereum," they usually mean WBTC or cbBTC — not actual Bitcoin. The asset didn't really move. Something else happened instead: real BTC was locked somewhere, and a new token was minted on Ethereum that represents a claim on it.
That distinction — between a native token and a wrapped one — matters more than it might seem. It determines who you're trusting, what the failure modes are, and whether the liquidity you're seeing is the real thing or a proxy. The confusion is understandable because wrapped tokens are designed to look identical to their native counterparts. Mostly, they do. Until a bridge gets exploited, or a custodian changes hands, or regulatory pressure hits the wrong intermediary.
How Native Tokens Work
A native token is issued directly by its home chain's consensus mechanism. ETH is native on Ethereum — its existence is enforced by Ethereum validators. BTC is native on Bitcoin — miners validate its ledger. SOL is native on Solana. There's no intermediary between you and the token's canonical existence on the chain.
The native token is also the unit of account for that chain's economic activity: it pays fees, denominates protocol-level staking, and serves as the base reference for everything else built on top. If the chain ceased to exist, the native token would cease to exist with it.
This creates a fairly clean trust model. You trust the chain's consensus. Nothing else sits between you and the asset.
How Wrapped Tokens Work
Wrapped tokens are a different animal. The mechanism: you deposit a native asset — say, BTC — with a custodian or bridge contract. That custodian locks it and mints a corresponding token on the destination chain, 1:1. WBTC on Ethereum is the most common example. When you want to exit, you burn the WBTC, and the custodian releases the underlying BTC.
The wrapped token is only as good as whatever is enforcing that 1:1 backing.
There are several variants of this model, and the trust assumptions differ significantly between them:
Custodial wrapping is what WBTC uses. BitGo (and now BiT Global, after a controversial 2024 custody transfer) holds the underlying BTC. You trust a regulated entity to maintain the peg. This is the most centralized model.
Smart-contract bridges lock the native asset in a bridge contract on the source chain and mint a bridged version on the destination. Wormhole and Synapse work this way. The trust assumption shifts from a custodian to the bridge's smart contract code and key management. These contracts hold enormous concentrated value — which is why they've been prime targets. Ronin lost $625M, Wormhole $320M, Nomad $190M.
Canonical L2 bridges are a subtler case. When you deposit ETH to Arbitrum via the official bridge, what you hold on Arbitrum is a wrapped representation pegged 1:1 to your L1 ETH. The trust model is actually strong here — it's secured by Ethereum's consensus — but it's still technically wrapping, and you can't use it natively on Ethereum until you withdraw.
One important exception worth calling out: USDC on multiple chains is not wrapped in the traditional sense. Circle uses a burn-and-mint model (Cross-Chain Transfer Protocol, or CCTP) — USDC is burned on the source chain and natively minted on the destination by Circle's coordination. No locked assets, no bridge honeypot. This makes USDC "native" on each chain it officially supports, which is a meaningfully different risk profile than WBTC.
Where the Constraints Live
The core constraint for wrapped tokens is custodial or bridge trust. It's unavoidable.
Even the most sophisticated decentralized bridging architecture has a point of failure — whether that's a multisig key set, an off-chain oracle network, a smart contract, or a regulated custodian. The larger the locked value, the more attractive the target.
A secondary constraint is liquidity fragmentation. WBTC and cbBTC both represent BTC on Ethereum, but they're different tokens. Their liquidity pools are separate. The depth of WBTC/ETH on Curve doesn't help you if you're holding cbBTC. Same underlying asset, fragmented markets.
Then there's the regulatory angle. Custodial wrapping puts an intermediary in the loop — and that intermediary may be subject to licensing requirements, asset freezes, or regulatory directives. WBTC's 2024 custody shift to BiT Global prompted Coinbase to launch cbBTC partly for this reason: institutional users wanted custodial BTC on Ethereum without that particular counterparty exposure.
What's Changing
The cbBTC launch in September 2024 introduced meaningful competition to WBTC in the custodial BTC wrapping market. Two custodially-backed options with different counterparty profiles.
More structurally interesting is the expansion of burn-and-mint models. Circle's CCTP removes the bridge honeypot problem for USDC. Newer assets are increasingly launching natively on multiple chains from day one using similar models, removing the need to wrap at all.
Intent-based bridging is also changing how this works in practice. Protocols like Across and the emerging ERC-7683 standard reframe cross-chain transfers: you specify what you want to receive on the destination chain, and a solver network figures out how to get it there. The solver handles the wrapped/native distinction on your behalf. For users, the token's origin increasingly becomes infrastructure-level plumbing.
Solver-based models introduce their own trust questions — solver centralization, MEV extraction, liveness guarantees. But the direction is toward abstracting the custodial complexity away from end users.
What Would Confirm This Direction
- cbBTC market cap closing the gap with WBTC as institutions choose counterparty diversity
- ERC-7683 solver network liquidity growing across major routes
- New cross-chain asset launches defaulting to burn-and-mint issuance over bridging
- L2 ecosystems deepening native asset support, reducing reliance on third-party bridge wrappers
What Would Break or Invalidate It
- A major bridge exploit at scale — particularly one hitting a canonical L2 bridge — could cause the market to significantly discount any wrapped asset and slow adoption of the model
- Regulatory action against custodial wrapping intermediaries in major jurisdictions
- Solver network failure in intent-based bridging — from centralization exploits or sustained MEV extraction — could drive users back toward direct custodial models
Timing Perspective
Now: The wrapped token ecosystem for BTC on Ethereum is live and consequential. WBTC and cbBTC together represent substantial BTC liquidity on Ethereum. Understanding the custodial distinction matters for DeFi risk assessment today.
Next: Burn-and-mint models and intent-based bridging are in early production and expanding. Worth watching whether cbBTC adoption displaces WBTC in major DeFi protocols.
Later: Native multi-chain issuance as the default for new assets. Whether wrapping becomes a legacy pattern or persists as the only viable route for existing L1 assets like BTC remains open.
Boundary Statement
This post explains the mechanism of native and wrapped tokens and the trust assumptions involved. It does not constitute a recommendation to use any specific bridge, custodian, or wrapped asset. Custodial risk thresholds, bridge audit status, and specific protocol TVL are tracked separately.
The mechanism works as described. Whether any particular wrapped asset is appropriate depends on factors outside this scope.
