Revision · Advanced & Rare Concepts

This part treated Bitcoin as what it actually is — an adversarial, eventually-consistent system, not a database with an API. Every topic followed one production reality all the way down, asking how a mechanism helps strangers agree on a ledger and how an adversary could abuse it.

What this part covered

• Transaction malleability — a transaction’s ID could change after you signed it, which broke naive withdrawal systems (the “Mt. Gox excuse”) and blocked payment channels until SegWit committed the txid without the signature.
• RBF, CPFP & the zero-conf myth — the mempool is a fee market, so a stuck transaction can be replaced (RBF) or pulled in by a child (CPFP), and accepting unconfirmed payments is a loaded gun with a real coffee-shop double-spend scenario.
• SIGHASH flags — a signature commits to a digest of chosen parts of the transaction, which is what enables crowdfunding and atomic swaps — and the infamous SIGHASH_SINGLE bug that can sign away money.
• Timelocks → HTLCs — nLockTime/CLTV (absolute) and nSequence/CSV (relative), combined with hashlocks, are the four obscure fields that make Lightning, cross-chain atomic swaps, and vaults possible.
• The UTXO set vs the chain — the set (current spendable coins, in RAM) is what drives validation speed and enables pruning and assumeutxo, while the chain is just history; this distinction also explains dust and dust attacks.
• Privacy & deanonymization — the chain is a permanent public graph, and heuristics like common-input-ownership and change detection unmask users, while CoinJoin and PayJoin fight back by poisoning those assumptions.
• Famous incidents & attacks — the Value Overflow Incident that minted 184 billion coins, the double-spend family (race, Finney, 51%), selfish mining, and transaction pinning as a modern Lightning threat.
• Taproot, Schnorr & MuSig2 — Schnorr signatures enable key aggregation (MuSig2) and MAST, so a complex multisig or script tree can look on-chain exactly like an ordinary single-key payment.
• Soft forks & the anyone-can-spend trick — new rules ship as tightenings that old nodes still accept, the mechanism behind P2SH, SegWit, Taproot, plus OP_RETURN and witness-data inscriptions.

The takeaway

The advanced track is really one long arms race: each mechanism that helps honest strangers coordinate is also something an adversary probes for edges. Understanding malleability, fee markets, timelocks, the UTXO set, privacy heuristics, and the Schnorr/Taproot frontier is what lets you build against Bitcoin instead of against your own wrong mental model. Next, the book steps outside Bitcoin to see these choices in contrast.