0 of 7 done
The layer everything else assumes. What problem blockchains solve, the primitives they’re built from, how state is represented, who gets to write, and how it all reaches the network. Chain-agnostic — nothing here is specific to Ethereum.
If you read only two notes in this folder, read 02 (the problem) and 05 (the answer).
Reading order
- what-web3-actually-is — [Beginner] — the vocabulary disentangled, the one technical claim underneath all of it, what you give up to get it, and the test that kills most blockchain proposals
- the-double-spend-problem — [Beginner] — why ordering (not detection) is the hard part, why Sybil resistance is the real problem, what was tried before 2008 and why it failed
- cryptographic-primitives — [Intermediate] — hashes as identity, Merkle proofs, recoverable signatures, and BIP-32/39/44. Assumes the cryptography course and covers only what’s blockchain-specific
- blocks-chains-and-state — [Intermediate] — block anatomy, why immutability is economic, UTXO vs the account model, and why state is derived rather than stored
- consensus — [Advanced] — PoW, PoS and BFT read through one question: what does an attack cost and who does it cost? Plus what a 51% attack can and cannot do
- networking-and-nodes — [Intermediate] — gossip, the public mempool, node types, client diversity, and the RPC-provider centralisation under most dapps
- tokens-coins-and-nfts — [Beginner → Intermediate] — a token is a row in a mapping; the approve footgun; decimals; and what an NFT actually is, said plainly
Related
- web3 curriculum map
- 02-ethereum-and-the-evm — the next layer up
- distributed systems — the parent field
- cryptography — the primitives, properly
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering