MASTERING-BITCOIN · Interactive Practice | Unit 15 · Video 3
| Concept | What it means | Why it matters |
|---|---|---|
| Single-use seal | A Bitcoin UTXO committed to be spent exactly once | Locks in an asset transfer; a 2-of-2 seal doubles as a Lightning channel |
| Pay-to-contract (P2C) | A tweaked public key that secretly commits to contract data | Invisible on-chain, but provable to whoever holds the secret |
| Client-side validation | Only the involved parties verify the full asset history | Bitcoin sees ordinary transactions; asset logic lives off-chain |
| Native vs Translated forwarding | Every hop knows the asset vs only the edge hops know it | Translated forwarding reuses Bitcoin's existing Lightning network |
The names taproot and Taproot Assets trip everyone up. One is a consensus upgrade that lives inside Bitcoin (activated in 2021). The other is a colored-coin protocol that sits on top, exactly like RGB.
Use the selector to see where each piece actually lives in the layer stack.
⚙ interactive visualization — coming to this page format soon
Notice: Only taproot sits inside the Bitcoin foundation block — it is part of consensus. Both RGB and Taproot Assets float above Bitcoin as separate layers. The similar names are by design (Taproot Assets borrows taproot's style), but the layers are completely different. Bitcoin's only native asset is still bitcoin.
To move a colored coin over Lightning, the payment travels through intermediate hops. The question is: which hops need to know about the asset?
Adjust the path length and switch the mode to see who must be "asset-aware" (gold).
⚙ interactive visualization — coming to this page format soon
Reflect: As you increase the number of hops in native mode, every single node turns gold — each must hold a balance of that specific asset, which fragments liquidity into a separate network per asset. In translated mode, the middle stays grey ("bitcoin only") no matter how long the path. This is why Taproot Assets is built around translated forwarding: it piggybacks on Bitcoin's existing Lightning economies of scale.
Translated forwarding hides a catch. The receiver holds a pending payment quoted in bitcoin but settling in the asset. As the exchange rate moves, the receiver can selectively accept when the rate favors them and reject when it doesn't — siphoning value from the adjacent hop that quoted the conversion.
Drag the exchange rate away from the quoted rate and watch the receiver's optimal decision and the resulting value flow.
⚙ interactive visualization — coming to this page format soon
Notice: The receiver never loses — when the rate moves in their favor they accept and pull value from the adjacent hop; when it moves against them they simply reject. That asymmetric "heads I win, tails I walk away" payoff is exactly what a free American call option looks like. It is an unsolved problem in this design space, which is why the field is still actively evolving.
Question 1
Both RGB and Taproot Assets let people issue stablecoins, tokens, and other assets "on Bitcoin." According to the video, what is Bitcoin's only native asset — the one written into its consensus rules?
✅ Correct! Bitcoin's only native asset is bitcoin; everything else lives in layers on top.
❌ Not quite. Colored-coin assets are never recognized by Bitcoin consensus — they sit on top.
Solution:
Bitcoin's rules acknowledge only bitcoin. Colored-coin protocols like RGB and Taproot Assets do not change this — they tag Bitcoin outputs with extra meaning that the network never sees. The asset logic lives entirely in separate layers on top of Bitcoin, so to the base chain everything still looks like ordinary bitcoin transactions.
Question 2
A common point of confusion: Taproot Assets is part of the Bitcoin consensus protocol, just like the taproot upgrade activated in 2021.
True or False?
✅ Correct! Taproot Assets sits on top of Bitcoin; only taproot itself is a consensus upgrade.
❌ Not quite. Don't let the names fool you — Taproot Assets is a layer on top, not part of consensus.
Solution:
False.
The similar names are intentional, but the layers are completely different.
Question 3
A colored-coin payment travels over Lightning using translated forwarding through a long path: Spender → Hop → Hop → Hop → Receiver.
Which hops need to be asset-aware (hold a balance of the asset)?
✅ Correct! Translated forwarding keeps the middle as a plain bitcoin core.
❌ Not quite. That describes native forwarding. Translated forwarding only needs the edge hops to know the asset.
Solution:
In translated forwarding, only the edge hops (next to the spender and the receiver) know the asset. Everyone in the middle just forwards bitcoin. This is the key advantage: it reuses Bitcoin's existing Lightning network and its economies of scale, instead of demanding a separate network per asset (which is what native forwarding requires, since native forwarding makes every hop asset-aware).
Question 4
The "free American call option" is described as a catch hiding inside translated forwarding. Which statement best captures why it gives the receiver an unfair, risk-free advantage?
✅ Correct! Accept the upside, reject the downside — that asymmetry is the free option.
❌ Not quite. The key is the asymmetric, risk-free choice the receiver makes as the rate moves.
Solution:
The receiver holds a pending payment quoted in bitcoin but settling in the asset. As the exchange rate moves, the receiver can accept when the rate favors them and reject when it doesn't, siphoning value from the adjacent hop that quoted the conversion. That asymmetric, no-downside payoff is exactly the profile of a free option on price, exercised at will. There is no known perfect fix — only practical mitigations that limit the damage.
Solved: 0 / 4