Skip to content
Financial Context Wiki

Canonical, Native, and Wrapped Tokens

A verification-first guide to token identity, issuer-native assets, protocol-designated bridge representations, same-chain wrappers, backing, redemption and executable exit value.

Updated

For educational purposes only; not investment, legal, or security advice. Token names, canonical labels, reserves and quoted prices do not guarantee identity, solvency, redemption, liquidity or legal treatment.

Direct answer

Canonical and wrapped are not opposite token classes. Canonical describes the token mapping or route designated by a particular ecosystem; wrapped describes a representation mechanism. A protocol-designated bridge token can itself be wrapped, while WETH is a same-chain wrapper and issuer-native USDC on a supported chain may use issuer-controlled burn and mint rather than bridge escrow.

Start with identity, not the symbol: chainId, native-asset marker or token contract, proxy implementation and block. Then determine who issues or designates it, what asset or liability backs it, who can mint, burn, pause or upgrade it, and whether an eligible holder can actually unwrap, redeem, bridge or sell it. Solvency, redemption availability and market liquidity are separate questions.

How it works

  1. Pin the snapshot: chain, chainId, native marker or token address, block and time, decimals, proxy implementation or codeHash, and the issuer or protocol documentation version. A name, symbol, logo or wallet token list is not identity.
  2. Classify on two axes. Identity status may be chain-native, issuer-native, protocol-designated or third-party. Mechanism may be a same-chain wrapper, lock-and-mint bridge claim, burn-and-mint transfer, custodial wrapper, vault share or liquidity-network receipt. One token can occupy more than one label.
  3. Trace the exact lineage and authority graph: origin asset, registered remote counterpart, escrow or burn contract, messenger or attester, destination minter, proxy admin, mint and burn roles, pause or denylist authority, timelock, limits and migration plan.
  4. Reconstruct the backing and liability ledger in raw and display units. For lock-and-mint, reconcile pair-eligible escrow with outstanding representation supply and in-flight claims. For issuer burn-and-mint, reconcile chain supplies and issuer liability; do not invent bridge escrow that does not exist.
  5. Verify the executable redemption lifecycle: who is eligible, direction, approvals, unwrap or burn, proof or attestation, finalization or claim, gas on each chain, fees, limits, pauses and failure recovery. A small test proves only that route and snapshot.
  6. Compare exit routes. Record executable DEX bid and depth, slippage, protocol and LP fees, gas, delay and custodian or exchange acceptance separately from reserve coverage. A backed token can trade below par, and a liquid price does not prove backing.
  7. Reconcile receipts, events, balances, supply, escrow, pending claims and remaining allowances. Keep native, wrapped, bridged and issuer-native balances separate; monitor implementation, roles, mapping, migration, pause, reserve disclosures and liquidity; and size exposure by the worst credible executable exit.

Worked examples

  • Coverage must include pending claims. Pair-eligible escrow is 2,500.000000 units, minted destination supply is 2,400.000000 units, and locked but not yet minted claims are 100.000000 units. Economic liabilities are 2,400 + 100 = 2,500, so adjusted coverage is 2,500 / 2,500 = 100%. Ignoring pending claims reports 2,500 / 2,400 = 104.1666666667%, a misleading surplus. Even correct coverage does not prove contract safety or immediate liquidity.
  • The same symbol can represent different claims. A holder owns 2,500 units of each of two contracts. The issuer-native contract has an executable bid of $0.998, worth 2,500 * 0.998 = $2,495; a third-party bridge contract has a bid of $0.920, worth 2,500 * 0.920 = $2,300. The difference is $195 despite matching name and decimals.
  • Wrapped does not imply cross-chain. A wallet starts with 5.000 ETH, deposits 3.000 ETH into a same-chain WETH contract and pays 0.002 ETH gas. It ends with 1.998 ETH and 3.000 WETH; wrapper reserve and supply are 3 / 3 = 100%; and economic exposure is 1.998 + 3.000 = 4.998 ETH before contract risk. Adding the reserve again would double count it.
  • Market exit and delayed redemption differ. For 10,000 tokens, the DEX bid is $0.985, price impact is 0.60%, LP or protocol fee is 0.10%, and gas is $12. Under that stated order, net proceeds are 10,000 * 0.985 * (1 - 0.006 - 0.001) - 12 = $9,769.05. An eligible redemption returns $9,987 after fees in 7 days; at a simple annual opportunity rate of 8%, present value is 9,987 / (1 + 0.08 * 7 / 365) = $9,971.7009519641, or $202.6509519641 more. This is not guaranteed arbitrage and omits default, finality, tax and price risk.

Risks

  • Using the wrong chain, native marker or token contract.
  • Trusting a spoofed symbol, name, icon or wallet token list.
  • Misreading decimals, raw units, supply or balance semantics.
  • Missing a proxy implementation, admin or code upgrade.
  • Accepting a stale registry, token pair, router or gateway mapping.
  • Losing control through a compromised issuer, mint, burn or attester role.
  • Treating commingled, pledged or encumbered reserves as pair-eligible backing.
  • Double counting escrow, representation supply and pending claims as separate value.
  • Omitting in-flight deposits, burns, withdrawals, fees or failed messages.
  • Assuming fee-on-transfer, rebasing or hook-bearing tokens follow standard accounting.
  • Encountering an issuer freeze, bridge pause, denylist, limit or censorship action.
  • Granting an excessive allowance or approving the wrong bridge spender.
  • Misreading source finality, message validity or destination execution status.
  • Depending on unavailable relayers, sequencers, provers, attesters or data.
  • Facing replay, double mint, failed burn, source reorg or accounting defects.
  • Discovering that direct issuer or bridge redemption is unavailable to the holder.
  • Suffering fragmented liquidity, depeg, slippage, MEV or insufficient market depth.
  • Omitting gas, protocol fees, delay, opportunity cost or custodian acceptance.
  • Being stranded in a deprecated contract or incomplete native-token migration.
  • Combining correlated chain, bridge, issuer, oracle, UI, RPC, tax, sanctions and custody risk.

Common misconceptions

  • Canonical always means issuer-native, official, trustless and safe.
  • Wrapped always means the token crossed a chain.
  • Tokens with the same symbol and decimals are fungible claims.
  • A one-to-one label, contract balance or supply figure proves redeemability.
  • Reserve backing guarantees immediate one-to-one cash value in every market and account.

Sources

Navigation

Search the wiki...