# Resources The reading list, annotated and mapped to the modules each resource serves. One framing note before diving in: this list treats blockchain as distributed systems + cryptography + economic incentives + developer-experience abstraction + product security. That's a deliberate choice — it's the combination that makes the field interesting to an engineer, and it's what the resources below are selected for. ## If you only use ten | **Priority** | **Resource** | **Why** | **Serves** | |---|---|---|---| | 1 | Bitcoin whitepaper | Original double-spend/PoW model | [[01 Replicated State Machines]], [[04 Consensus]] | | 2 | Stanford CS251 | Best academic map | [[01 Replicated State Machines]]–[[04 Consensus]] | | 3 | Ethereum.org docs | Canonical modern reference | nearly every module | | 4 | Mastering Ethereum | Best developer book | [[03 Blocks, Hashes, and History]], [[05 Execution and Smart Contracts]], [[07 Wallets and Account Abstraction]] | | 5 | ERC-4337 docs | Account abstraction/wallet UX | [[07 Wallets and Account Abstraction]] | | 6 | OP Stack docs | Production rollup architecture | [[09 Scaling - Rollups and Data Availability]] | | 7 | Arbitrum docs | Alternative L2 architecture | [[09 Scaling - Rollups and Data Availability]] | | 8 | DeFi MOOC | Financial invariants, adversarially | [[11 DeFi, Stablecoins, and Governance]] | | 9 | Ethernaut | EVM security basics | [[05 Execution and Smart Contracts]], [[12 Security and Incentive Design]] | | 10 | Damn Vulnerable DeFi / Paradigm CTF | Adversarial protocol thinking | [[12 Security and Incentive Design]] | Product-specific resources (Privy docs, WalletConnect, WebAuthn) live in [[Wallet Infrastructure Roles (Privy)]]. ## Core protocol foundations **Bitcoin whitepaper.** Short, dense, still the cleanest statement of the double-spend problem, proof-of-work, hash-linked history, and probabilistic [[Finality]]. Read it first; do not overstay — it teaches the skeleton, and most modern work is Ethereum/wallet/product-shaped. → [[01 Replicated State Machines]], [[03 Blocks, Hashes, and History]], [[04 Consensus]] **Stanford CS251 (Blockchain Technologies).** The best academic starting point: distributed consensus, smart contracts, economics, scalability, with Bitcoin and Ethereum as case studies. For a distributed-systems reader it lands as "consensus with adversarial economics." → Phase 1 of the [[Learning path]] ## Ethereum fundamentals **Ethereum.org developer docs.** The canonical reference to return to constantly. Read in this order: nodes and clients, accounts, transactions, gas, smart contracts, consensus, blocks, finality, rollups, data availability, account abstraction. Notably clear on the consensus-client/execution-client separation. → [[03 Blocks, Hashes, and History]] through [[09 Scaling - Rollups and Data Availability]] **Mastering Ethereum.** The best developer-oriented book: wallets, keys, transactions, EVM, contracts, token standards, tooling. Use for fundamentals, not for the current roadmap — the field moves faster than print. → [[05 Execution and Smart Contracts]], [[07 Wallets and Account Abstraction]] ## Account abstraction and wallets **ERC-4337 docs.** The practical center of account abstraction: UserOperations, bundlers, paymasters, EntryPoint, smart accounts. The bridge from crypto wallets to normal product accounts. → [[07 Wallets and Account Abstraction]], and hands-on via Project 4 in [[Projects to Build]] **WalletConnect docs** and **WebAuthn/passkeys material.** Wallet-app session protocol; the credential layer under embedded wallets. → [[07 Wallets and Account Abstraction]], [[Wallet Infrastructure Roles (Privy)]] ## Rollups, DA, and modular architecture **Ethereum.org rollup + DA docs.** First stop: optimistic vs ZK rollups, validiums, sidechains, and data availability as separate topics. → [[09 Scaling - Rollups and Data Availability]] **EIP-4844 / blobs explainers.** Why rollup data got cheap: blob-carrying transactions, commitments visible to the EVM, data outside execution. The one-line takeaway: Ethereum scaling is the separation of execution from data publication and settlement. → [[Data Availability]] **OP Stack docs.** A production optimistic rollup, in the open: sequencer, batcher, fault proofs, L1/L2 messaging. → [[09 Scaling - Rollups and Data Availability]] **Arbitrum docs.** The contrast case: sequencer inbox, batch posting via calldata or blobs, rollup vs AnyTrust trust modes. Reading two architectures teaches more than rereading one. → [[09 Scaling - Rollups and Data Availability]], [[10 Bridges and Interoperability]] **Celestia docs.** The modular decomposition (execution / settlement / consensus / DA) and the DA-sampling intuition. Not core to product work; excellent for architecture literacy. → [[09 Scaling - Rollups and Data Availability]], [[Data Availability]] ## Security **Ethernaut.** First hands-on lab: reentrancy, delegatecall, tx.origin, access control, storage layout, forced ETH. Start during Phase 2; finish during Phase 5. → [[05 Execution and Smart Contracts]], [[12 Security and Incentive Design]] **Damn Vulnerable DeFi.** Protocol-level adversarial reasoning: flash loans, oracle manipulation, governance attacks, liquidation logic. Where you start thinking like an attacker. → [[11 DeFi, Stablecoins, and Governance]], [[12 Security and Incentive Design]] **Paradigm CTF.** The deep end — do not start here. A few writeups, studied carefully, sharpen instincts disproportionately. → [[12 Security and Incentive Design]] **Post-mortems (Rekt.news and primary sources).** The field's case law: Ronin, Wormhole, Nomad, and whatever happened last month. Each one is a [[Trust Assumptions|trust assumption]] that someone discovered the hard way — which makes them some of the most instructive reading available. → [[10 Bridges and Interoperability]], [[12 Security and Incentive Design]] ## Cryptography and ZK **Boneh & Shoup, *A Graduate Course in Applied Cryptography*.** The serious reference. Read selectively — hash functions, MACs, signatures, commitments, key exchange — and resist proving every theorem unless the work turns cryptography-heavy. → [[02 Cryptographic Primitives]] **ZK learning materials.** Learn enough to hold the shape of the idea: statement, witness, succinct verification, validity proof vs fraud proof. Circuit engineering is its own career, and you don't need it unless you're heading toward proving infrastructure. → [[02 Cryptographic Primitives]], [[09 Scaling - Rollups and Data Availability]] ## DeFi and economics **DeFi MOOC.** The structured treatment: AMMs, lending, stablecoins, oracles, liquidations, governance, MEV. The useful lens is not yield — it is how financial invariants get encoded in adversarial state machines. → [[11 DeFi, Stablecoins, and Governance]] **Uniswap docs and whitepapers.** The cleanest canonical primitive: constant-product AMM, LP positions, concentrated liquidity, oracle implications. → [[11 DeFi, Stablecoins, and Governance]] **MakerDAO docs.** The canonical crypto-collateralized stablecoin: vaults, liquidation, redemption, and the full taxonomy of what "backed" means. → [[11 DeFi, Stablecoins, and Governance]] ## Do, don't just read The two highest-return activities on this whole page are not reading at all: 1. **Build the indexer** (Project 2 in [[Projects to Build]]) — it teaches more practical blockchain backend engineering than most courses combined. 2. **Run a node, or dig into your RPC provider's trust model** — keep at it until the difference between accessing the chain and verifying it stops being a slogan and becomes something you can feel. → [[08 Nodes, RPCs, and Indexers]] --- The ordered journey: [[Learning path]] · The map: [[Blockchain Home]]