What Are Wrapped Tokens?

In brief

“Wrapped” covers at least two importantly different arrangements:

1. Same-chain adapters. WETH represents ETH deposited in a contract on Ethereum so applications can handle it through an ERC-20-like interface. Wrapped SOL similarly places native SOL in a Token Program account on Solana. The backing and the representation stay on one chain.
2. Representations across ledgers. WBTC represents BTC held under a custodian-and-merchant system while token units exist on supported smart-contract networks. A bridge may instead lock a token on one chain and mint a corresponding token on another.

An issuer’s burn-and-mint transfer can move native issuance between supported chains without producing a wrapped token. Circle describes CCTP this way for native USDC: source-chain USDC is burned and destination-chain USDC is minted after an attestation. That is different from a third party locking USDC and issuing its own bridged claim.

Wrapping changes the form in which an asset can be used. It does not make the original ledger entry travel, guarantee a permanent one-to-one market price, or copy the original asset’s liquidity to the new token.

Why native assets need adapters

ETH is the native asset of Ethereum, not an ERC-20 contract. It therefore has no ERC-20 approve, allowance, or transferFrom. Many applications were designed around ERC-20 transfers, so they need a token-shaped version of ETH.

The canonical WETH9 contract accepts ETH through deposit() and credits the sender’s WETH balance. withdraw(amount) reduces that balance and sends ETH back. Its reported total supply is the ETH balance held by the contract. This is a same-chain accounting adapter: the contract’s ETH is the backing for WETH recorded by that same contract.

Uniswap v2 made the reason concrete. Its core pairs support ERC-20 tokens and do not contain special logic for native ETH; WETH is used so ETH can participate through the common token interface.

The same-chain design avoids a cross-chain validator or custodian, but it is not risk-free. A user still has to identify the intended WETH contract, and any contract bug or incompatible imitation can break the expected conversion. A token merely named “WETH” is not necessarily the established deployment for that network.

Wrapped SOL is also same-chain

Solana’s official token documentation calls WSOL “SOL held in a token account for the Token Program’s native mint.” SOL is stored as lamports in the account, while the Token Program exposes a token amount that programs can transfer using token instructions. SyncNative updates that token amount after SOL is deposited above the account’s rent-exempt reserve.

WSOL is therefore not SOL bridged from another network. It is native SOL placed in an account shape understood by Solana token programs. Its mechanics are not WETH bytecode copied to Solana.

Cross-ledger representations add another promise

Bitcoin UTXOs cannot be read or spent as Ethereum ERC-20 balances. A system that makes bitcoin-denominated tokens available to Ethereum applications must create a new token record and establish why it should be redeemable for BTC.

WBTC is a documented custodial example. Its official mint-and-burn documentation assigns separate roles to users, approved merchants, and a custodian. BTC is placed in custody before corresponding WBTC is minted; for redemption, WBTC is burned before BTC is released through the merchant process. End users do not directly command the custodian simply by calling an Ethereum contract.

The project publishes reserve addresses and aggregates token issuance in a transparency dashboard. That makes quantities inspectable, but it does not remove the operational and governance assumptions: users still depend on correct custody, authorized minting, merchant access, and the stated redemption process.

A bridge-created wrap has a different mechanism. Commonly, a contract locks tokens on chain A and another contract mints a representation on chain B after a message is accepted. The representation’s backing then depends on both the locked assets and the bridge’s validation, finality, upgrade, and key assumptions. The Bridges article examines those transport and trust designs in depth.

Native, wrapped, and bridged can coexist

The same economic asset may appear in several forms on one chain:

• a token issued natively on that chain by its issuer;
• a token locked elsewhere and represented by a bridge;
• a custodial token backed by an asset on another ledger;
• a same-chain adapter for the chain’s native gas asset.

These are not interchangeable merely because a wallet displays the same ticker. For example, Circle-native USDC and a third party’s bridged USDC may both target one dollar, but they have different contracts and redemption paths. CCTP’s native burn-and-mint model specifically avoids wrapped USDC; it should not be described as lock-and-mint wrapping.

Backing is not market price

A one-to-one conversion rule describes a mechanism, not every trade. A wrapped token can trade above or below the reference asset because:

• traders doubt the backing or mint controls;
• redemption is slow, restricted, paused, or costly;
• the destination market has little depth;
• the bridge, custodian, or issuer is impaired;
• the reference asset and wrap are priced on different venues at different times.

Reserve coverage and liquidity answer different questions. A wrap can be fully backed yet difficult to sell quickly in a thin pool. It can also trade near parity for a time even while its backing is disputed. Oracles and collateral systems that accept the wrap must decide which contract and market they are actually measuring.

How to inspect a wrapped asset

Start with identifiers and redemption, not branding:

1. Which contract or mint address is this?
2. What is the original asset, and on which ledger does it exist?
3. Is this a same-chain adapter, custodial representation, or bridge token?
4. What action creates and destroys units?
5. Where can backing be verified, and what is not proven by that check?
6. Who can mint, pause, upgrade, freeze, or change custodians?
7. Who may redeem, on what terms, and for which asset?
8. How deep are the actual markets for this exact token address?

What wrapped does not mean

Wrapped does not mean decentralized, risk-free, liquid, or permanently pegged. It does not mean that native BTC now exists in an Ethereum account, or that ETH has physically moved to another chain. It also does not mean every cross-chain transfer creates a wrapped asset; issuer burn-and-mint and inventory-based payments can produce a destination asset without a lock-and-mint wrap.