Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu
Lesson 10 / 21 · Expert

Native bitcoin and wrapped claims

Follow the asset and the extra trust assumptions.

14 MIN WITH PRACTICEREAD → TRY → REFLECTNO WALLET NEEDED

By the end, you’ll be able to…

  • Explain why a Bitcoin-linked token is not a Bitcoin UTXO.
  • Map issuance, redemption and host-chain dependencies.
The idea, at a glance

Similar exposure. Different dependencies.

NativeBitcoin outputs and spending conditions
WrappedA representation on another chain
RedeemA separate promise, process and dependency
Holding a wrapped token is not the same as controlling native Bitcoin outputs.

Start with the settlement system

Native bitcoin is represented by spendable outputs under Bitcoin’s rules. Lightning uses Bitcoin-based channel arrangements with additional operational assumptions. A token on another chain that references BTC is a different technical object. Its symbol, logo or quoted price does not make it settle directly as a Bitcoin output.

Follow the representation back to its promise

A wrapped or custodial representation needs an explanation of issuance, underlying assets, redemption rights and who can change or interrupt the arrangement. Some designs involve custodians; others involve bridges or other verification mechanisms. Identify the actual product rather than treating all wrappers as identical. A reserve report does not by itself prove every holder’s immediate ability to redeem.

Add the lending layer separately

If that token becomes collateral in a lending contract, the user adds smart-contract, oracle, liquidity and liquidation exposure. Holding the host-chain private key does not remove these dependencies. For a paper comparison, draw native BTC, the representation, the collateral contract and the borrowed asset as distinct boxes. Label each controlling party and exit condition. No specific wrapped asset is approved by this course, and a familiar ticker is not sufficient evidence for a real collateral route.

Your turn / A paper experiment

Practice on paper

A brochure calls a BTC-linked token “bitcoin with extra utility.” Which questions would reveal the omitted dependencies?

I’ve tried it — show the worked answer

Ask which chain records it, what backs it, who can issue or restrict it, who is eligible to redeem, what evidence verifies reserves and which contracts or bridges an exit requires. If used as collateral, also identify the oracle, liquidation rule and available loan liquidity.

Want to explore with buttons and instant feedback? Try the practice lab ↗

Think it through

Make a choice. Discover why.

Choose an answer and check the explanation. You can retry as often as you like. These are practice questions, not a test of mastery; answers are not saved or sent.

1. Does holding a wrapped token’s private key eliminate issuer risk?
  • Yes
  • No
Read the explanation

No. Key control and the representation’s promise are separate.

2. Is native BTC itself an ERC-20 token?
  • Yes
  • No
Read the explanation

No. Bitcoin outputs and ERC-20 contract balances are different systems.

One idea to take with you

Count each added dependency before calling a design sovereign.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.