If you've ever moved BTC to Ethereum to use it in DeFi, you've used a wrapped token. Bridging wrapped tokens explained in plain language: it's a token on one chain that represents an asset from another chain, backed 1:1 by the underlying. Below is the full breakdown of how wrapped tokens work, the risks to manage, and which bridges are safe in 2026.
What Exactly Is a Wrapped Token?
A wrapped token is a synthetic representation of an asset from a different blockchain. The most common example: WBTC (Wrapped Bitcoin) on Ethereum. Each WBTC is backed by 1 BTC held in reserve by a custodian. The custodian publishes proof of reserves, and the WBTC:BTCR ratio stays at 1:1 under normal conditions.
Wrapped tokens exist because blockchains can't natively read each other. Bitcoin's blockchain has no way to know what's happening on Ethereum, and vice versa. Wrapped tokens create a "tether" between chains: lock BTC on Bitcoin, mint WBTC on Ethereum. Burn WBTC on Ethereum, unlock BTC on Bitcoin.
How the Bridging Process Works
When you bridge wrapped tokens, three things happen behind the scenes:
- Lock: you deposit the underlying asset (or a wrapped version) into the bridge contract on the source chain.
- Verify: the bridge protocol verifies the deposit. Verification methods vary: lock-and-mint (most common), burn-and-mint, or liquidity-pool based.
- Mint: the bridge mints an equivalent amount of the wrapped token on the destination chain and sends it to your wallet.
The reverse (redeeming the wrapped token) burns the wrapped version on the destination chain and unlocks the underlying on the source chain. The process takes 1-30 minutes depending on the bridge and chain speeds.
The Main Types of Bridges
Not all bridges work the same way. Bridging wrapped tokens explained in terms of architecture:
Lock-and-Mint Bridges
The most common. You lock tokens on Chain A, the bridge mints equivalent wrapped tokens on Chain B. Examples: Wormhole, LayerZero/Stargate, Multichain (now defunct). The risk: if the lock contract on Chain A gets hacked, every minted wrapped token on Chain B becomes undercollateralized.
Burn-and-Mint Bridges
Used when the token has a native version on both chains. You burn the token on Chain A, the bridge mints it on Chain B. Examples: USDC native burn-mint between Ethereum and Solana. Lower risk because there's no separate custody layer.
Liquidity Network Bridges
No locking or minting. The bridge has liquidity pools on both chains, and a relayer network handles transfers. Examples: Across, Hop Protocol, Connext. The risk: pool depth. If the destination pool is shallow, large transfers get high slippage.
Optimistic Bridges
Newer architecture. Assume transactions are valid unless challenged within a dispute window (similar to Optimistic Rollups). Examples: Across, Synapse (optimistic mode). Lower fees, slightly higher latency.
Risks of Wrapped Tokens
Bridging wrapped tokens carries three categories of risk. None are fully eliminable, but you can manage them.
1. Custody Risk
Who holds the underlying asset? For WBTC, the answer used to be a centralized custodian (BitGo). After the 2024 BitGo governance change, it now uses a more decentralized merchant network. If the custodian fails or misplaces the BTC, every WBTC holder is at risk. The mitigant: use wrappers with transparent proof-of-reserve and a strong reputation (WBTC, tBTC, renBTC before its sunset).
2. Smart Contract Risk
The bridge code is the largest attack surface in DeFi. The five largest crypto hacks of all time were all bridge exploits:
- Ronin Bridge: $625M (2022)
- Wormhole: $320M (2022)
- Nomad: $190M (2022)
- Harmony Horizon: $100M (2022)
- Multichain: $130M (2023)
Total bridge hacks exceed $2.8 billion. The mitigant: only use bridges with multiple audits from top firms, a public bug bounty, and a track record of surviving stress tests.
3. Depeg Risk
The wrapped token can trade below the underlying asset if trust in the bridge or custodian is shaken. WBTC briefly traded at $0.95 on some DEXs in 2024 when the BitGo governance issues surfaced. The mitigant: monitor wrapper-vs-underlying prices, exit to the underlying if the spread widens above 0.5%.
Safe Wrapping: Best Practices in 2026
Here's the framework for bridging wrapped tokens with the lowest possible risk:
- Prefer native issuance: if USDC is natively available on the destination chain, use it instead of bridged USDC.e. Native assets have no bridge risk.
- Use the largest bridges by TVL: LayerZero/Stargate, Wormhole, Chainlink CCIP, and Across handle 80%+ of safe volume. They have the audits, the bug bounties, and the track record.
- Avoid multichain-style bridges: if the bridge's team is anonymous, the audits are missing, or the TVL has dropped 50%+, stay away.
- Bridge during low congestion: weekend and Asian-hours bridges face less congestion, lower fees, and faster finality.
- Don't bridge more than 10% of your portfolio in one go: split large transfers into multiple smaller bridges to limit single-point-of-failure exposure.
Wrapped vs Native: When to Use Each
Native assets are always safer. But not every asset is native to every chain. Decision matrix for 2026:
- USDC, USDT, ETH: native on Ethereum, Base, Arbitrum, Polygon, Avalanche, Solana. Use native.
- BTC: WBTC on Ethereum, BTC.b on Avalanche, Native BTC on Botanix, Bitlayer. Stick to WBTC for liquidity; use BTC.b if you're farming on Avalanche.
- Solana assets (SOL, JUP, JTO): wrapped on Ethereum via Wormhole. Use native SOL if you're trading on Solana, wrapped only if you need to bridge to Ethereum.
- TON, SUI, APT, SEI: limited DeFi, mostly use the native versions. Wrapping is rarely worth it.
The Best Wrapped Token Bridges in 2026
Based on audits, TVL, and track record:
- LayerZero / Stargate: $4B+ in omnichain volume. Audited by Trail of Bits, Zellic, Spearbit.
- Wormhole: $40B+ in cumulative bridged volume. Audited by Trail of Bits, Certora. Recovered from a $320M hack via whitehat rescue.
- Chainlink CCIP: institutional-grade. Used by SWIFT, ANZ, and major banks for tokenized assets.
- Across Protocol: optimistic verification, lowest fees for L2-to-L2 transfers. Audited by OpenZeppelin.
- Synapse: solid L2-to-L2 bridge, optimistic mode available.
Final Word
Bridging wrapped tokens is one of the most useful skills in DeFi, but it's also one of the most dangerous. The bridge code is the soft underbelly of the entire crypto ecosystem, and hackers know it. Stick to audited bridges, prefer native issuance, never bridge more than you can afford to lose, and monitor the wrapper-vs-underlying spread. Done right, wrapped tokens unlock DeFi across chains. Done wrong, you lose everything in a single hack.