Mastering Bitcoin
The technical reference for how the protocol actually works.
Summary
Antonopoulos wrote the standard technical reference on the Bitcoin protocol, aimed at developers and at people who need to understand how the system actually works rather than what it is claimed to do.
The content covers the protocol mechanics in detail: keys and addresses and the elliptic curve cryptography behind them; wallet types and hierarchical deterministic key derivation; the structure of transactions, including inputs, outputs, the unspent transaction output model and the scripting language; the blockchain data structure and Merkle trees; the peer-to-peer network and how transactions and blocks propagate; mining, proof of work, difficulty adjustment and the consensus mechanism that resolves competing chains; and the security assumptions the system rests on, including what a majority attack could and could not achieve.
The book's distinguishing quality is that it explains why each design decision was made and what it trades off, rather than only describing the mechanism. The treatment of consensus in particular explains that agreement emerges from independent verification by every node combined with the economic cost of producing blocks, rather than from any coordinating authority.
It is a technical book requiring programming background, published by O'Reilly, and the second edition is substantially revised. It covers Bitcoin specifically and not the wider cryptocurrency ecosystem, and it makes no investment case. Its limitations are date: it predates the scaling debate's resolution, SegWit, the Lightning Network's development and the subsequent protocol changes, and the second edition addresses some but not all of these.
Key takeaways 7
- Bitcoin consensus emerges from independent verification by every node combined with the economic cost of producing blocks, not from any coordinating authority.
- The unspent transaction output model means a bitcoin balance is a set of unspent outputs rather than an account with a number in it.
- Proof of work makes rewriting history expensive in proportion to how far back the rewrite goes, which is what gives confirmations their meaning.
- Difficulty adjustment maintains a constant average block interval regardless of how much computing power joins or leaves the network.
- Bitcoin's scripting language is deliberately limited, which trades functionality for predictability and for the absence of unbounded execution.
- Hierarchical deterministic wallets derive all keys from a single seed, which changes what must be backed up and what an attacker who obtains it can do.
- A majority of mining power would allow transaction censorship and reversal of recent blocks but not theft of coins or creation of invalid transactions.
Who should read it
Developers and technically capable readers who need to understand the Bitcoin protocol's actual mechanics and design trade-offs.
Where it sits in the reference 2
Who recommended it 1
Similar books 6
Chosen by shared topics, the entries that hold them, and the people who recommended both.
