Wrapped tokens exist because blockchains don't talk to each other.
Bitcoin can't be used in Ethereum DeFi. Not because of a technical oversight — because they're separate networks with different rules, different validators, and no shared state. When you submit a transaction on Ethereum, Bitcoin nodes don't see it. Full stop.
Wrapped tokens are how the ecosystem gets around this. The short version: lock a real asset somewhere, mint a token on a destination chain that represents it, use that token as a proxy. It's not Bitcoin on Ethereum — it's a claim on Bitcoin, held on Ethereum.
That distinction matters. A lot.
The Basic Mechanism
Wrapped Bitcoin (WBTC) is the clearest example. Here's how it actually works.
A user wants to use their Bitcoin in Ethereum DeFi — to earn yield, collateralize a loan, or provide liquidity. They can't send BTC to an Ethereum address directly. The networks are incompatible at the protocol level. Instead, they go through a WBTC merchant — a registered entity in the WBTC ecosystem. The merchant takes their BTC, sends it to a custodian (BitGo holds the majority of WBTC reserves), and the custodian mints an equivalent amount of WBTC as an ERC-20 token. One WBTC equals one BTC, always.
Once minted, WBTC behaves exactly like any other ERC-20 token. It can be deposited into Aave as collateral, traded on Uniswap, supplied to a liquidity pool. The DeFi protocol doesn't know or care that WBTC represents Bitcoin — it just sees a token with a price feed.
To unwrap: burn the WBTC, the merchant signals the custodian, the custodian releases the underlying BTC. Supply contracts accordingly.
The peg is maintained by redeemability. If WBTC traded at a meaningful discount to BTC, arbitrageurs would buy WBTC cheaply, redeem it for real BTC, and capture the spread. That arbitrage mechanism keeps the 1:1 relationship intact under normal conditions.
Where the Risk Actually Lives
This is where the wrapped token story gets more complicated.
The WBTC mechanism is custodial. BitGo holds the BTC. If BitGo is hacked, goes bankrupt, or acts improperly — the WBTC backing disappears. The tokens continue to exist on Ethereum, but they're backed by nothing. This isn't a theoretical risk. It's the same structural exposure that made FTX's collapse so damaging for assets that depended on FTX as custodian.
In 2023, concerns around WBTC specifically escalated when BitGo announced a partnership with Justin Sun's BiT Global as a new custody co-signer. Several DeFi protocols paused WBTC as accepted collateral in response. The episode demonstrated that the real variable in any custodial wrapped token is trust in the underlying custodian — and that trust is dynamic, not fixed.
Bridge hacks are a related but distinct risk. Bridges move tokens between chains using locking-and-minting logic similar to WBTC. The Ronin bridge lost $625M. Wormhole lost $320M. Harmony lost $100M. These weren't edge cases — they were predictable outcomes of large amounts of value held in smart contracts that weren't as battle-tested as the protocols built on top of them. Bridge code is where wrapped-token-style logic gets concentrated, and concentration creates targets.
The Decentralized Alternative
The logical response to custodial risk is: remove the custodian.
Several projects have attempted this. RenBTC (now defunct) used a decentralized custodian network. The cryptographic assumptions turned out to be more fragile than expected, and the project collapsed when its parent company (Alameda Research) did.
tBTC, from Threshold Network, uses threshold signatures — a cryptographic approach requiring multiple independent keyholders to agree before BTC can be released. No single party holds the full private key. The model is more robust than a single custodian, though it introduces its own complexity and trust assumptions around the keyholder set.
The honest assessment: decentralized wrapping is harder than it looks. The cryptographic primitives exist, but keeping keyholders honest across a wide range of market conditions is an unsolved problem at scale. tBTC is live and growing, but WBTC still dominates by roughly a 10x margin in circulating supply.
What's Changing
Two structural shifts are worth tracking.
Bitcoin-native DeFi has accelerated interest in how BTC gets used on other chains. The growth of Ordinals, Runes, and Bitcoin Layer 2 experiments has created demand for BTC in DeFi contexts — and new questions about whether wrapping on Ethereum is the right long-term path, or whether Bitcoin-native protocols eventually absorb that demand. This is early and largely unresolved.
Intent-based routing systems (CoW Protocol, UniswapX) are beginning to abstract cross-chain mechanics from users. In an intent-based system, you specify what you want — "supply BTC as collateral on Aave" — and solvers compete to execute the best path. Wrapping might happen behind the scenes, invisible to the user. If this matures, the wrapping step becomes an implementation detail even if the custodial or cryptographic risk remains.
What Would Confirm This Direction
Trust-minimized alternatives (tBTC, threshold signatures) consistently gaining market share against WBTC. Intent-based systems showing measurable growth in cross-chain volume with no corresponding increase in user-visible wrapping steps. No major custodian failures across a full market cycle.
What Would Break It
A WBTC custodian failure that triggers a peg break and systemic DeFi liquidations. Another major bridge hack at the scale of Ronin or Wormhole. Bitcoin-native smart contracts maturing to the point where wrapping on Ethereum is no longer the dominant path for BTC DeFi exposure.
Timing
Now: WBTC is live and dominant. Custodial risk is current and active. If you're holding WBTC as DeFi collateral, the custodian is a real variable in your risk model — not a background assumption.
Next: Trust-minimized alternatives are maturing and worth monitoring. The BiT Global custody episode created structural demand for alternatives that didn't exist two years ago.
Later: Intent-based routing may abstract wrapping away from users entirely. That's a multi-year development arc, not a near-term shift.
Scope Note
This explanation covers the mechanism and where the risk lives. It doesn't address whether any specific protocol's wrapped token exposure is appropriate for a given use case. The custodial risk landscape shifts when custodian participants change — the mechanism above is stable, but the actors operating within it are not.
