By Eco research. Updated Apr 2026.
​

Wrapped tokens are blockchain representations of assets from a different chain or protocol, created when a bridge locks the original asset in a custody contract and mints a corresponding token on the destination chain. WBTC (Wrapped Bitcoin) locks BTC on the Bitcoin network and issues an ERC-20 token on Ethereum backed 1:1. WETH wraps native ETH to conform to the ERC-20 standard. Each wrapped token inherits both the value of the underlying asset and the risk profile of the bridge that created it.
​

Wrapped tokens are synthetic representations of assets that exist on a different blockchain, created by locking or burning the original asset through a bridge contract. The wrapped version tracks the price of the original asset and can be redeemed by reversing the bridge process. WBTC holds roughly $8.8 billion in locked BTC as of April 2026 according to DeFiLlama, making it the largest wrapped token by TVL and one of the most significant custodial dependencies in DeFi.
​

The term "wrapped" comes from the analogy of encasing one asset in a new contract interface. Native ETH predates the ERC-20 standard and lacks its transfer and approval functions. WETH (Wrapped Ether) is the most-used wrapped token by raw transaction volume because every DeFi protocol on Ethereum that uses ERC-20 tokens requires WETH instead of raw ETH. The WETH contract (0xC02aaA39b223FE8D0a0e5C4F27eAD9083C756Cc2) is one of the highest-volume contracts on Ethereum by call count.
​

Wrapped tokens are distinct from the broader category of blockchain bridges in that the bridge is the mechanism and the wrapped token is the result. A bridge can move assets cross-chain without producing a wrapped token, using a burn-and-mint model that issues native tokens on the destination. Whether the result is "wrapped" or "native" depends entirely on which minting authority controls the destination token and whether the original asset is destroyed or merely locked.
​

Lock-and-mint bridges hold the original asset in a custody contract on the source chain and issue a corresponding synthetic token on the destination chain. The supply of wrapped tokens on the destination equals the supply of locked assets on the source. To redeem, the user burns the wrapped token and the bridge releases the underlying asset. WBTC, the BitGo-backed Wrapped Bitcoin on Ethereum, is the canonical lock-and-mint example with multi-institutional custody.
​

The mechanics work in five steps. First, the user sends the original asset (say BTC) to a custodian address controlled by the bridge. Second, the bridge's oracle or validator set confirms the deposit. Third, the bridge's mint contract on the destination chain (Ethereum) creates an equivalent amount of the wrapped token (WBTC). Fourth, the user receives WBTC and can use it across DeFi protocols, collateral markets, or DEX liquidity pools. Fifth, to exit, the user burns their WBTC on Ethereum, the bridge validates the burn, and the custodian releases BTC on the Bitcoin network.
​

WBTC specifically uses a three-party model: BitGo as custodian of the underlying BTC, a network of merchants who can mint and burn WBTC, and a decentralized autonomous organization that governs the contract. The custodian model means BTC reserves are visible on the Bitcoin blockchain at a publicly auditable address. BitGo holds custody of the underlying BTC, which means WBTC carries BitGo counterparty risk. A BitGo insolvency, hack, or regulatory action affecting their Bitcoin holdings would directly affect WBTC holders.
​

wstETH (Wrapped Staked ETH from Lido) follows a different variant of the lock-and-mint model. Users stake ETH through Lido, receiving stETH, a rebasing token that increases in balance as staking rewards accrue. wstETH wraps stETH into a non-rebasing format, fixing the token count while the exchange rate (wstETH per stETH) increases instead. This makes wstETH usable as collateral in lending protocols like Aave and Compound that cannot handle rebasing tokens. As of April 2026, Lido holds approximately $20.9B in staked ETH TVL per DeFiLlama, making wstETH one of the highest-liquidity wrapped tokens across Ethereum and rollups.
​

Burn-and-mint bridges destroy the token on the source chain and issue a fresh, native version on the destination chain, eliminating the locked-reserve dependency of lock-and-mint. Circle's Cross-Chain Transfer Protocol (CCTP) uses this model for USDC: when a user bridges USDC from Ethereum to Base, the Ethereum CCTP contract burns the USDC and transmits an attestation to the Base contract, which mints an equal amount of native USDC. No USDC is ever locked; the total supply across chains reflects actual issued supply.
​

The difference from lock-and-mint is important for risk profiles. A lock-and-mint bridge holds custodial reserves that are a single target for exploits. If the reserve is drained, all wrapped tokens lose backing simultaneously. Burn-and-mint removes the reserve entirely. The security model shifts from "are the reserves safe?" to "is the attestation mechanism trustworthy?" CCTP's attestation is controlled by Circle, which also controls USDC issuance, so the trust model is consolidated rather than distributed.
​

Not all stablecoins can use burn-and-mint. The issuer must control minting on every destination chain. Circle controls USDC issuance on every supported chain, enabling CCTP. Tether controls USDT issuance similarly, but as of Q1 2026 Tether has not launched a CCTP-equivalent for USDT. Most USDT bridging still uses lock-and-mint mechanisms via third-party bridges. USDC total supply stands at approximately $77.3B as of April 2026 (DeFiLlama), with a significant portion distributed across chains via CCTP-issued native tokens rather than locked bridge reserves.
​

Wrapped tokens carry two primary risk categories beyond those of the underlying asset: bridge exploit risk, where an attacker drains the locked reserves, and depeg risk, where the wrapped token loses its 1:1 exchange rate against the underlying. Secondary risks include smart contract bugs in the wrapper contract itself and custodian counterparty risk for centrally managed bridges like WBTC. These risks are distinct from the market risk of the underlying asset.
​

Bridge exploits have caused some of the largest losses in DeFi history. The Ronin Bridge hack in March 2022 drained approximately $625M in ETH and USDC from the bridge reserves backing Ronin's wrapped tokens, per Chainanalysis post-mortems. The Wormhole exploit in February 2022 extracted approximately $320M in wrapped ETH by manipulating the signature verification contract. The Nomad bridge hack in August 2022 drained roughly $190M by exploiting a validation bug that allowed anyone to replay bridge messages. In each case, holders of wrapped tokens backed by those bridges faced either total loss or extended redemption delays while the protocols assessed their exposure.
​

Depeg risk is distinct from exploit risk. A wrapped token can depeg even without an active exploit if market participants lose confidence in the bridge's solvency or if the redemption mechanism is paused. WBTC trading at a discount to native BTC occurred briefly during the FTX contagion period in November 2022, when rumors about BitGo's exposure to FTX spread. The discount was temporary and resolved once BitGo confirmed its BTC reserves were intact, but it illustrated that wrapped token prices are driven by both asset value and bridge confidence simultaneously.
​

Smart contract bugs in the wrapper contract itself represent a third vector. wstETH's non-rebasing conversion, for example, requires correct calculation of the exchange rate between stETH and wstETH. A bug in the rate calculation would cause incorrect collateral valuations across every lending market that uses wstETH. Lido's contracts have been audited by multiple firms, but audit coverage does not eliminate deployment risk entirely.
​

Users should prefer native assets over wrapped tokens whenever the native version is available on the destination chain and the bridge premium, conversion cost, or risk premium of the wrapped version is not justified. For USDC, native CCTP-issued tokens are always preferable to bridge-locked wrapped USDC because burn-and-mint USDC carries no reserve risk. For ETH, native ETH is preferable to bridge-wrapped ETH on rollups that settle to Ethereum, since the rollup's native ETH derives its security directly from Ethereum consensus rather than a bridge contract.
​

The practical decision tree is straightforward. First, check whether the destination chain issues native tokens. Most major EVM rollups (Base, Arbitrum, Optimism) receive native USDC via Circle's CCTP, native USDT via Tether's direct issuance, and native ETH via the rollup's canonical bridge. Second, if only a wrapped version exists, check the bridge reputation and audit history. The L2Beat bridges dashboard tracks bridge security configurations and risk ratings. Third, if using a wrapped version, understand the redemption path: how long does the challenge or finality window take, and what happens if the bridge pauses?
​

For cross-chain DeFi users, wrapped tokens are often unavoidable. Many DEX liquidity pools, particularly on non-Ethereum chains, hold bridge-issued wrapped assets as the only available form. WBTC remains the dominant way to use Bitcoin value in Ethereum DeFi. In those contexts, the risk is the cost of accessing the liquidity, and users who want Bitcoin exposure in Aave or Uniswap V3 accept WBTC's custodial risk as part of that choice.
​

Intent-based bridges, where solvers fulfill cross-chain transfer requests from their own inventory before settling asynchronously, can often deliver native destination tokens even when the source chain only has a wrapped version. The solver holds native assets on the destination and fronts them to the user, then rebalances their inventory separately. The user receives native USDC on Base without the bridge-locked-WUSDC route ever touching their wallet.
​

Across Protocol, one of the larger intent-based bridge implementations by volume, operates this way. Across relayers hold liquidity on multiple chains and fill user requests by sending native tokens from their existing balance. The rebalancing uses the Across optimistic oracle (based on UMA) to verify the source-chain deposit before the relayer is repaid. As of Q1 2026, Across reports over $1B in weekly transfer volume across its intent-based routing, according to the Across volume dashboard.
​

Li.Fi aggregates multiple bridge routes, including both lock-and-mint and burn-and-mint bridges, and selects the optimal path for a given token and chain pair. When a native route via CCTP exists, Li.Fi routes through it by default. When only a lock-and-mint route exists, Li.Fi surfaces the bridge provider and estimated security rating so users understand what they're using. The aggregator model means users interact with a single interface rather than managing multiple bridge protocols manually.
​

The key limitation of intent-based bridging for wrapped tokens is inventory: if a solver has no native assets on the destination chain, they may fall back to a canonical wrapped-token route or decline to fill the order. High-velocity transfers or unusual token pairs often encounter this limit. For stablecoin payments specifically, Eco's routing infrastructure uses Hyperlane as its live cross-chain messaging layer and CCTP as the internal USDC transport, which means USDC transfers complete as native tokens on supported chains without wrapped-USDC intermediaries.
​

Bridging to a wrapped token and then unwrapping follows two separate transactions, each with its own fee and confirmation requirement. For most users, bridge frontends handle both steps in a combined flow, but understanding the underlying mechanics helps when a bridge fails midway or when gas costs make a two-step approach uneconomical.
​

The bridging step sends the original asset to the source-chain bridge contract. For lock-and-mint bridges, this is a deposit transaction that locks funds and triggers the minting process on the destination. Confirmation times range from a few seconds for optimistic bridges with a large relay network to 15-30 minutes for bridges that wait for finality. The user receives the wrapped token on the destination after the bridge's validation completes.
​

The unwrapping step, if needed, converts the wrapped token back to the canonical form for that chain. WETH to ETH unwrapping is a single contract call to the WETH contract's withdraw function, costing a few thousand gas on Ethereum. wstETH to stETH conversion uses Lido's wstETH contract unwrap function. For lock-and-mint bridges, unwrapping means initiating a burn-and-redeem through the same bridge: the user burns the wrapped token on the destination and receives the native asset on the source after the bridge's finality window elapses.
​

Circle's Cross-Chain Transfer Protocol fundamentally changes USDC bridging by eliminating the locked-reserve model that characterizes most wrapped tokens. CCTP burns native USDC on the source chain and mints native USDC on the destination, with Circle attesting to the burn before the destination contract mints. Users receive native Circle-issued USDC on the destination, not a bridge-wrapped token, which removes the bridge exploit risk from the equation for this specific asset.
​

Before CCTP, bridging USDC to Polygon or Arbitrum produced a bridge-wrapped version, commonly displayed in wallets as "USDC.e" or "USDC (Bridged)". These versions have historically traded at small discounts to native USDC during periods of bridge stress and have sometimes required migration when bridges upgrade or deprecate their contracts. CCTP native tokens avoid both issues.
​

CCTP launched on Ethereum and Avalanche in April 2023 and has since expanded to Arbitrum, Base, Optimism, Polygon, Solana, and several other chains. As of Q1 2026, Circle has processed billions of USDC transfers via CCTP across its supported chains, according to Circle's CCTP documentation. For developers building cross-chain payment flows with USDC, CCTP is the recommended integration path over third-party lock-and-mint bridges where it's available. The blockchain bridges article covers the broader bridge landscape in more detail.
​

WETH (Wrapped Ether) has the same market value as ETH and is always redeemable 1:1 through the WETH contract, but it is a distinct ERC-20 token, not native ETH. DeFi protocols that require ERC-20 tokens use WETH. Native ETH is used for gas payments. Wrapping and unwrapping cost a few thousand gas, which at typical 2026 gas prices amounts to less than $0.01 per conversion.
​

Yes. A wrapped token can depeg if the bridge holding its backing reserves is exploited, paused, or loses market confidence. WBTC briefly traded at a small discount in November 2022 due to concerns about BitGo's FTX exposure. The peg recovered once reserves were verified. Depeg risk is most acute during bridge stress events or when redemptions are paused by bridge operators.
​

USDC.e (or bridged USDC) is a lock-and-mint wrapped version of USDC created by third-party bridges before CCTP existed. Native USDC is issued directly by Circle's contracts on the destination chain via CCTP burn-and-mint. Most major chains now support native USDC. USDC.e remains in circulation on some chains but carries bridge custodial risk that native USDC does not.
​

Bridge confirmation times vary by mechanism: optimistic bridges with instant liquidity (like Across) can deliver funds in under two minutes for standard amounts; canonical rollup bridges (Arbitrum, Optimism) take seven days to finalize exits; CCTP-based USDC transfers settle within roughly 20 minutes to a few hours depending on source-chain finality requirements. High-value transfers on lock-and-mint bridges may wait for multiple block confirmations for security before minting.
​

Sources and methodology. WBTC TVL and Lido TVL sourced from DeFiLlama on April 29, 2026. Bridge exploit figures (Ronin, Wormhole, Nomad) sourced from Chainalysis post-mortems and publicly reported settlement values. CCTP launch dates and supported chains verified against Circle CCTP documentation. USDC supply sourced from DeFiLlama April 29, 2026. Across volume sourced from the Across Protocol volume dashboard, Q1 2026.
​