Mastering Bitcoin Unlocking Digital Cryptocurrencies (Andreas M. Antonopoulos)（Z-Library）

【One-Line Pitch】 A practical, code-first tour of how Bitcoin actually works under the hood—keys, transactions, the peer-to-peer network, mining, and the Lightning layer—written for developers, engineers, and technically curious readers who want to build on or reason about the protocol rather than just hold the currency. 【Book Arc】 - **Opening (~0%–10%)**: Frames Bitcoin as a decentralized trust network rather than mere "digital money," then walks a newcomer from wallet setup through a first transaction, establishing vocabulary and the big picture before any code. - **Early (~10%–35%)**: Explains how Bitcoin works end to end—transactions, blocks, mining, and confirmations—by tracking a real transaction through the network, then introduces the reference client (Bitcoin Core) and how to compile and run it. - **Middle (~35%–55%)**: Moves into the developer toolkit: the Bitcoin Core JSON-RPC API and language wrappers, then the cryptography of keys and addresses (elliptic curves, Base58Check, key formats, multisig and P2SH addresses). - **Late (~55%–85%)**: Dives into the protocol internals—transaction structure and scripts, the P2P network and node types, the blockchain and consensus, and mining/proof-of-work—plus wallet technology including HD (BIP32) wallets and seeds. - **Ending (~85%–100%)**: Extends the building blocks into higher-level applications: Segregated Witness, payment channels, hash locks and timelocks (HTLCs), and the Lightning Network for routed off-chain payments. 【Book Arc note】The excerpt set is thin on the exact chapter boundaries for the later stages; the progression above follows the table of contents and glossary signals rather than confirmed page ranges. 【Key Takeaways】 - **Bitcoin is a trust network, not just a currency** (Opening): the author's central reframing—consensus emerges from participant interaction instead of a central authority, which is why the book treats it as a platform for applications. - **Follow one transaction to understand the whole system** (Early): tracking a single payment from wallet to confirmation is the book's teaching device, making abstract concepts like mempool, blocks, and confirmations concrete. - **Keys and addresses are the real user-facing cryptography** (Middle): private/public key pairs, elliptic curve math, and encoding formats (Base58Check, BIP-38, P2SH) explain why address handling is where most security mistakes happen. - **Bitcoin Core is both a node and a programmable interface** (Middle): building from source and calling the JSON-RPC API (directly via curl or through wrappers like python-bitcoinlib) is the gateway to programmatic Bitcoin work. - **Scripts make transactions flexible** (Late): addresses can represent scripts, not just public keys, enabling multisignature and conditional spending—the foundation for everything built later. - **Confirmations are probabilistic, not absolute** (Early): the six-confirmation convention reflects accumulated computation, a mental model readers must internalize before trusting settlement assumptions. - **HD wallets solve key management at scale** (Late): hierarchical deterministic key derivation (BIP32) and seeds let one backup regenerate an entire wallet tree—essential for both users and wallet builders. - **Layer-2 payments rest on hash locks and timelocks** (Ending): HTLCs plus bi-directional payment channels enable the Lightning Network to route payments between peers with no direct channel, showing how protocol primitives compose into new systems. 【Reading Tips】 - **Skim the build/install chapter** (compiling Bitcoin Core, configure flags) unless you plan to run a node immediately; the concepts matter more than the exact commands, which age quickly. - **Deep-read the keys/addresses and transaction/script chapters**—these are the load-bearing technical sections and repay slow, hands-on reading with the code examples. - **Run the code snippets** where feasible (RPC calls, key generation in Python); the book is explicitly example-driven, and typing the examples cements the mental model. - **Use the Quick Glossary early**—terms like HTLC, locktime, and HD seed appear before their full explanations, so a first pass through the glossary prevents confusion. - **Treat the Lightning/SegWit material as a bridge, not a manual**: it explains the primitives and design intent; expect to consult dedicated resources for production layer-2 work. 【Coverage Limits】 These excerpts are dominated by front matter, table of contents, glossary, and early chapters, so this guide's picture of the later protocol and Lightning chapters is inferred from headings and glossary entries rather than full text; specific chapter-level detail there is not covered by the excerpts.