Cross-Chain Bridges and Wrapped Assets
A blockchain can only natively understand its own assets, so moving value from one chain to another means locking it up on the first chain and minting a synthetic IOU on the second — and that IOU is only as trustworthy as the bridge that issued it.
Prerequisites: Blockchains and Consensus
Bitcoin is a native asset on the Bitcoin blockchain. Ethereum smart contracts have no way to directly read or move it, because Ethereum has no idea Bitcoin's ledger exists — the two chains do not talk to each other. If you want "Bitcoin" usable inside an Ethereum application, you cannot actually move the bitcoin there. Instead, someone locks real bitcoin up on the Bitcoin chain and, in exchange, mints a token on Ethereum that represents a claim on it. That token is wrapped Bitcoin, and the system that does the locking and minting is a bridge.
A bridge doesn't move an asset between chains — it locks the original on chain A and mints a synthetic representation on chain B. The wrapped token's value depends entirely on the promise that the lock-up is real and redeemable, which is a trust assumption, not a cryptographic guarantee like the blockchain itself provides.
How the lock-and-mint actually works
Step one: a user sends real BTC to a custody address controlled by the bridge. Step two: the bridge's off-chain system verifies the deposit and instructs a smart contract on Ethereum to mint an equivalent quantity of wrapped BTC (WBTC or similar) to the user. Step three, in reverse: the user burns the wrapped token on Ethereum, and the bridge releases the locked BTC back on the Bitcoin chain.
The wrapped token is designed to trade at a 1:1 peg with the original because it is redeemable for it, the same logic that keeps a warehouse receipt trading near the value of the grain it represents. But the peg holds only as long as the market believes the custody is sound.
Worked example: what a bridge exploit actually breaks
A bridge holds 120,000 ETH in a custody contract on Ethereum, against which it has minted 120,000 wrapped ETH on a separate chain, each redeemable 1:1. An attacker finds a flaw in the bridge's verification logic and tricks it into minting an extra 80,000 wrapped ETH on the destination chain without depositing any real ETH.
- Before the exploit. 120,000 ETH locked, 120,000 wrapped ETH outstanding — fully backed, 1:1.
- After the exploit. Still 120,000 ETH locked, but now 200,000 wrapped ETH outstanding.
- True backing ratio. , so each wrapped ETH is now backed by only 60 cents of real collateral.
- Market reaction. Once this becomes known, the wrapped token typically trades toward that 0.60 ratio rather than 1:1, because the last people to redeem will find the custody empty — a race exactly like a bank run.
This is precisely the mechanism behind the largest bridge hacks in crypto history: the exploit is rarely a flaw in the destination chain itself, but in the bridge's verification of what happened on the source chain.
What this means in practice
Every wrapped asset carries two layers of risk stacked on top of each other: the risk of the underlying asset, and the risk of the specific bridge that issued the wrapper. A trader holding "wrapped BTC" on a given chain should ask who controls the custody keys, how withdrawals are verified, and what happens if that bridge is ever compromised — because a hack on the bridge, not on Bitcoin itself, is what would break the peg. This is also why sophisticated users track bridge total-value-locked and audit history the way credit analysts track a bond issuer's balance sheet.
"Wrapped" does not mean "as safe as the original." A wrapped token inherits the smart-contract risk, custody risk, and governance risk of the specific bridge that minted it — bridge hacks are the single largest category of crypto exploit by dollar value, precisely because a bridge is a concentrated pool of locked collateral controlled by a much smaller, much more attackable system than the underlying blockchain itself.
Further reading
- Chainalysis, 'Cross-Chain Bridge Hacks' report
- Zamyatin et al., 'SoK: Communication Across Distributed Ledgers'