Interoperability & cross-chain

wrapped asset

A wrapped asset is a token on one chain that stands in for an asset that lives on another, backed one-for-one by the real thing held somewhere else. The most famous is WBTC: an ERC-20 on Ethereum that represents bitcoin, so that Bitcoin's value can flow through Ethereum's DeFi even though the Bitcoin network knows nothing about Ethereum. Each WBTC is supposed to be matched by exactly one BTC locked under the wrapper's custody.

Wrapping exists because chains cannot natively hold each other's assets, and because protocols expect a uniform token interface. You cannot deposit raw BTC into a Uniswap pool or an Aave market on Ethereum; you deposit WBTC, which behaves like any ERC-20. The same logic produces wrapped ETH (WETH) so that native ETH conforms to the ERC-20 standard, and a vast array of bridged tokens that represent assets from other chains on a destination chain.

The wrapped token is exactly as trustworthy as whatever backs it. With WBTC the backing is a custodial reserve held by a centralized institution, so you trust that custodian to keep the BTC and honour redemptions. With bridge-issued wrapped tokens the backing is a lock contract, so you trust that bridge's security. Two failure modes recur: the backing is stolen or mismanaged (the peg collapses), or several incompatible wrapped versions of the same underlying fragment liquidity across bridges. Always ask: who or what actually holds the real asset, and can they be trusted to give it back?

'Wrapped' is not a guarantee of backing — it is a claim of backing. The asset is only as sound as the custody arrangement: a wrapped token whose reserve is opaque or whose bridge is weak can trade at par right up until it suddenly cannot.