Wrapped Tokens: Minting, Custody and Redemption Risk

The claim inside the ticker

Wrapping solves a compatibility problem. A native asset may not exist on the chain where a user wants to deploy it, or may not follow the token standard that the application requires. A wrapper creates a token that does, and ties its value to the original.

The tie is a claim. There are three broad designs, and each puts the claim in a different place.

A contract holds the asset. The wrapper contract receives the native asset and issues a token; unwrapping returns the asset. The claim is on the contract’s code and its balance. This is the minimal design, and it has no external custodian.

A custodian holds the asset, and merchants mint against it. The user delivers the asset to an intermediary, the intermediary instructs the custodian, and a token is issued. The claim runs through two institutions and a legal structure.

A wrapper wraps another token. The underlying is itself a claim — a staking position, a receipt, a fund share — and the wrapper issues a more usable version of it. Here the claim’s value depends on the inner token’s mechanics as well as the wrapper’s.

Each design has a different failure mode, and the ticker conceals which one you hold.

Design one: the contract wrapper

The simplest wrapper is a contract that accepts the native asset and mints an ERC-20 token at a fixed rate, usually 1:1, then burns the token and returns the asset on unwrap.

The trust surface is narrow and specific: the contract’s code, its upgrade rights if any, and the chain’s own security. There is no custodian to default and no merchant to refuse. The risks that remain are the familiar ones — a bug in the contract, an admin key with upgrade or pause powers, and the possibility that the wrapped asset is accepted as collateral in places that do not account for its wrapper status.

This design is the exception rather than the rule for assets that live on another chain. A contract on chain B cannot hold an asset on chain A without a custodian, a bridge or a light client proving the other chain’s state.

Design two: the custodial wrapper

For assets that exist on their own chain, the wrapper usually involves a custodian. WBTC’s about page describes the product as a direct 1:1 representation of Bitcoin, secured through cold storage, multi-signature authentication and on-chain, publicly verifiable audits. It also cites proof of reserves and public mints and burns.

The flow has more steps than the contract wrapper:

1. A user delivers bitcoin to a merchant.
2. The merchant sends it to the custodian.
3. The custodian mints WBTC to the merchant.
4. The merchant forwards it to the user.

Redemption reverses the sequence: the token is burned, and the bitcoin is released. Each step is a relationship, and each relationship has conditions — minimums, fees, processing times, eligibility, and the merchant’s own operational reliability.

The transparency measures address a specific question: are the tokens outstanding matched by the bitcoin held? Proof of reserves and public mint and burn records answer that at a point in time. They do not answer a different question: if a large share of holders redeemed at once, would the custodian process them promptly and in what order?

That second question is the one that matters in a stress event, and it is a liquidity and operations question rather than an accounting one.

Design three: wrapping a claim

Lido’s documentation describes wstETH as the non-rebasable, value-accruing counterpart of stETH. The distinction is mechanical and it matters for how a position is measured.

stETH rebases: the balance updates as staking rewards and penalties accrue. wstETH does not: the balance stays fixed and the value of each unit increases against stETH. Lido’s documentation states this directly — the wstETH balance does not change on its own but increases in value against stETH.

The consequence is arithmetic. Suppose the exchange rate is 1 wstETH = 1.16 stETH. Wrapping 10 stETH yields:

• 10 / 1.16 = 8.6207 wstETH

If the rate later rises to 1.20, the same balance is worth:

• 8.6207 × 1.20 = 10.3448 stETH

That is a 3.45% gain, which is exactly the rate change (1.20 / 1.16 − 1 = 3.45%). No tokens were added. The gain is in the exchange rate.

This design choice is why wrappers of claims are popular as collateral: a contract can hold a token whose balance does not move. The cost is that any system measuring the position must read the exchange rate rather than the balance. A system that treats 8.6207 wstETH as 8.6207 stETH understates the position and misprices the collateral.

The exit is what anchors the price

A wrapper’s market price can differ from the underlying’s value, and the size of the difference is set by the exit.

If redemption is open, cheap, fast and available to the holder, the gap is bounded by the cost of doing it. If it is conditional, the gap can widen to the market’s estimate of the cost and risk of reaching it.

The frictions are the same family that produce stablecoin depegs: eligibility, minimum sizes, processing times, business hours, network compatibility and capacity. A wrapped asset whose redemption requires a merchant relationship and a custodian’s processing window is not a liquid claim at 3 a.m. on a Sunday, whatever its price says.

Two practical readings follow:

• A discount is not automatically a bargain. It may be the market pricing the exit correctly. The question is whether you can reach the exit more cheaply than the market assumes.
• A premium is not automatically a squeeze. It may reflect demand from users who cannot or will not use the unwrapped asset, and who are paying for the wrapper’s utility.

The risk list, in order of visibility

Contract and admin risk. Visible in code and documentation, often auditable. Upgradeability and pause powers are the parts to look for.

Custody risk. Visible in legal structure and attestations, but only partly. The question of what happens in the custodian’s insolvency depends on segregation and jurisdiction, not on the token’s price.

Redemption risk. Visible in terms and conditions, and usually the first to bind in a stress event.

Merchant and operational risk. Each intermediary can slow or stop processing. A wrapper with several merchants can route around a failure; one with a single merchant cannot.

Liquidity risk. The secondary market may be deep in normal conditions and thin exactly when redemption is slow, because market makers reduce size when flow is one-sided. The spread, depth and slippage guide covers how that depth is measured.

Composability risk. A wrapped asset used as collateral can be liquidated if its market price moves, even if the underlying has not moved. The wrapper introduces a second price that can be hit independently.

What to check before holding one

1. Where is the underlying, and who can touch it? A contract address, a custodian, or a legal entity. Each implies a different recovery path.
2. What are the redemption conditions? Minimum size, fees, processing time, eligibility and supported networks. If you cannot redeem, you are a secondary-market holder whether or not you intended to be.
3. What does the transparency cover? Mint and burn records show supply. An attestation shows holdings at a date. Neither shows queue capacity under stress.
4. Does the wrapper rebase, and does every system it touches know that? A non-rebasing wrapper read as a rebasing one misstates collateral.
5. Can the contract be upgraded or paused? And by whom.

For the underlying mechanics of moving value between chains, the finality guide covers when a transfer is actually settled, and the tokenised treasuries guide covers how the same wrapper logic applies to fund shares and government exposure. For the wrapper’s accounting cousin, the reserve attestation guide separates what a proof can establish from what it cannot.

How these sources were checked

The description of WBTC as a direct 1:1 representation of Bitcoin, the cold storage and multi-signature custody, the publicly verifiable audits, and the proof-of-reserves and public mint and burn language come from WBTC’s About page, retrieved 2026-10-24. The description of wstETH as the non-rebasable, value-accruing counterpart of stETH, and the statement that its balance does not change while its value rises against stETH, come from Lido’s token integration guide, retrieved 2026-10-24. The assessment of systemic risk from wrapped assets, including the point that wrapped versions can be exploited, comes from ethereum.org’s Bridges page, retrieved 2026-10-24.

The exchange-rate arithmetic is computed from the stated rates. No wrapper fee, minimum redemption size, merchant spread or custody arrangement is asserted as fact for any particular product; where a number appears, it is labelled as an assumption or derived from the stated rates.