精通比特币《第二版》 (wizardforcel) (Z-Library)

【One-Line Pitch】 A hands-on technical tour of how Bitcoin actually works—keys, addresses, transactions, scripts, the network, and mining—aimed at developers and technically curious readers who want to understand the machinery beneath the currency rather than just trade it. 【Book Arc】 - **Opening (~0%–8%)**: Frames Bitcoin's origin, the double-spend problem, and the user/transaction/miner model, then walks a concrete Alice-to-Bob payment to show how value moves as a chain of transactions. - **Early (~8%–31%)**: Moves into practice—building and configuring Bitcoin Core, querying node state via RPC, and the cryptographic core of ownership: private/public keys, elliptic-curve math, addresses, and Base58Check encoding. - **Early–Middle (~31%–46%)**: Covers wallet standards and usability—HD wallets, BIP-32/39/43/44, mnemonic seeds, passphrases, hardware wallets—then dissects transaction structure, UTXOs, and the stack-based Script language. - **Middle (~46%–62%)**: Explores programmable money in depth: multisig, P2SH, OP_RETURN, time locks (CLTV/CSV), plus the peer-to-peer network, address discovery, Bloom filters, and the blockchain/Merkle-tree data structure. - **Late (~62%–77%)**: Turns to consensus and mining—proof-of-work, difficulty retargeting, forks (soft and hard), mining pools and protocols (Stratum, GBT), and the economics of running a node. - **Ending (~77%+)**: Addresses security practice and ecosystem evolution—physical key storage, hardware encryption, multisig custody—and how consensus changes are proposed and activated (BIP-9 signaling). 【Key Takeaways】 - **Bitcoin solves double-spending without a central authority** (Opening): a distributed proof-of-work "election" every ~10 minutes lets the network agree on transaction state—this is the founding insight the whole book builds on. - **Ownership is cryptographic, not stored on the network** (Early): keys live in your wallet, and possession of a private key equals control of funds; addresses are derived abstractions, not accounts. - **One private key can yield two different addresses** (Early): compressed vs. uncompressed public keys produce distinct addresses, a subtlety that matters when importing keys and scanning the chain. - **Transactions are chains of UTXOs, not balances** (Middle): inputs reference prior outputs, and verifying or fee-calculating requires retrieving the referenced UTXO—there are no senders, receivers, or balances at the protocol level. - **Script makes Bitcoin programmable** (Middle): the stack-based language enables P2PKH, multisig, P2SH, OP_RETURN, and time locks, expressing conditions far beyond simple payments. - **Consensus emerges from cumulative work** (Late): nodes always extend the chain with the greatest cumulative proof-of-work, so temporary forks resolve as more blocks accumulate. - **Mining is a probabilistic race measured in work** (Late): difficulty retargeting keeps block times stable, and pools coordinate hashpower through protocols like Stratum and GBT. - **Security is a practice, not a feature** (Ending): hardware wallets, multisig, and careful backup/recovery planning (including passphrase risk) are essential for real-world custody. 【Reading Tips】 - **Deep-read the key/address and transaction/script chapters** (Early–Middle): these are the conceptual load-bearing walls; skim the build/configure and RPC command listings if you only need concepts. - **Treat code and hex dumps as illustrations, not memorization targets**: focus on what each step proves (e.g., how a signature unlocks a UTXO) rather than the exact byte strings. - **Pause on the Script and time-lock sections**: the stack execution model and CHECKMULTISIG quirks are the hardest spots; work through the Mohammed multisig example slowly. - **Connect mining to consensus**: read proof-of-work, difficulty, and forks together—they only make sense as one system. - **Carry the security chapter into practice**: if you handle real funds, revisit wallet standards and backup design after finishing. 【Coverage Limits】 These excerpts are stratified and uneven; some areas (e.g., detailed later chapters on advanced applications, Lightning, or specific BIP mechanics) are only partially represented, so this guide reflects the sampled material rather than the full book.