MASTERING-BITCOIN · Interactive Practice
| Mechanism | Role | What it answers |
|---|---|---|
| Single-use seal (a UTXO) | A UTXO can be spent only once | WHEN the asset moves |
| Pay to contract (P2C) | Contract hidden inside a tweaked public key | HOW the asset moves |
| Client-side validation | Only the recipient checks the history | WHO verifies the transfer |
Pay-to-contract key tweak (Taproot-style):
where is the underlying public key, is the contract, is the generator point, and is the tweaked key that looks completely ordinary on-chain.
Intrinsic asset = bitcoin itself (value lives on-chain). Extrinsic asset = a stock, gold, or deed that lives off-chain — Bitcoin only anchors a claim to it.
Conceptual question: Which assets live natively on Bitcoin, and which are only pointed to by a colored satoshi?
Pick an asset below and watch where it lands in the classification tree. The blockchain never holds extrinsic assets — it only anchors a claim to them.
⚙ interactive visualization — coming to this page format soon
Reflect: Only bitcoin is intrinsic — it is the one asset whose value truly lives on the chain. Everything else is extrinsic: the blockchain anchors a claim, while the real stock, gold, or deed lives outside it.
Conceptual question: Why is an unspent transaction output (UTXO) like a tamper-evident shipping seal?
Toggle the switch to spend the UTXO. Just like breaking a seal, spending can happen only once — and that single irreversible event is what associates the asset transfer with the chain.
⚙ interactive visualization — coming to this page format soon
Notice: An intact seal means the asset is still at rest. The one-time break (the spend) is the digital equivalent of opening the package — it marks exactly when the asset moved. But the seal alone never tells you how the asset was split or where it went. For that, we need the contract.
Conceptual question: How can a contract be committed on-chain while staying completely invisible?
Adjust Alice's underlying key and pick a contract. The system tweaks the key with a commitment to the contract: . Watch how the resulting on-chain key looks like an ordinary key no matter what contract is chosen — full nodes never learn a contract exists.
⚙ interactive visualization — coming to this page format soon
Reflect: Change the contract from a one-line transfer to a long legal deed — the on-chain tweaked key is still just an ordinary-looking key. Because nodes never validate the contract, it can be arbitrarily long, in any language. The chain commits to it without ever reading it. The seal said when; the contract says how; and the chain stays blind to both.
Question 1
In colored coins, what plays the role of the tamper-evident shipping seal that can only be opened once?
✅ Correct! A UTXO can be spent only once — the digital equivalent of breaking a seal.
❌ Not quite. Think about what has the 'spend it only once' property, just like a seal.
Solution:
A single-use seal is implemented as a UTXO (unspent transaction output). Like a tamper-evident seal, a UTXO can be spent only once, and that single, irreversible spend is what associates the asset transfer with the chain. It tells you exactly when the coins move.
Question 2
True or False: The real-world asset (e.g., the gold or the stock) is stored directly on the Bitcoin blockchain.
✅ Correct! Only a satoshi marker and an ordinary key are on-chain — the asset lives off-chain.
❌ Not quite. Remember the first trap: the asset is not stored on-chain, only a marker is.
Solution:
False. Only a tiny satoshi marker and an ordinary-looking public key sit on-chain. The asset itself — and its contract — live off-chain. The blockchain never holds the gold, stock, or deed; it merely anchors a claim to them. Bitcoin becomes a notary for assets it never has to understand.
Question 3
After Bob spends a colored UTXO, what actually determines who controls the asset next?
✅ Correct! The contract defines control and can point to entirely unrelated outputs.
❌ Not quite. Recall the third trap: holding the UTXO does not automatically make you the owner.
Solution:
The contract defines control, and it can point anywhere. The pay-to-contract spend can split the color so that part goes to an output with no visible link to Bob or Alice at all. So the next owner is not necessarily whoever received the UTXO Bob spent — receiving a UTXO does not automatically make you the owner.
Question 4
Who actually verifies that a colored coin transfer is legitimate, and which Bitcoin upgrade was shaped by the same key-tweaking idea?
✅ Correct! Client-side validation puts verification in the recipient's hands, and P2C-style tweaking shaped Taproot.
❌ Not quite. Recall that only relevant parties validate — and that P2C influenced Taproot's key tweaking.
Solution:
Verification is client-side: the recipient's software validates the full prior history locally (the P2C key, contract terms, seal UTXO, and chain of transfers). Bitcoin nodes can't and don't — they don't even know a contract exists.
The pay-to-contract foundations (tweaking a public key with a commitment) helped shape the Taproot upgrade, which uses similar key tweaking.
Solved: 0 / 4