0 of 7 done
The applied section. How the contract layer connects to an actual product — and the constraints (no query language, seconds-long writes that can fail after payment, a hosted RPC in the middle) that shape every dapp architecture.
The note that saves the most rework is 04-indexing-and-events. Discovering that you cannot query a blockchain after designing your product is a common and expensive surprise.
Reading order
- the-dapp-architecture — [Intermediate] — the honest diagram, what belongs on-chain vs in Postgres, the stack as of 2026, and counting the centralised components
- wallets-and-connection — [Intermediate] — what a wallet is, connection vs authentication, the three signature types, and the UX problems with no good answer yet
- reading-and-writing-chain-state — [Intermediate] — the RPC surface, multicall, simulate-before-send, and the seven-state transaction machine most dapps model as two
- indexing-and-events — [Intermediate] — why you cannot query a blockchain, the indexer pipeline, reorg handling, and designing contracts to be indexable
- decentralised-storage — [Intermediate] — IPFS solves integrity, not persistence; Arweave, fully on-chain, and why NFT images disappear
- oracles — [Intermediate] — the trust you can’t avoid, the Chainlink checks everyone omits, and why there is no safe on-chain randomness
- account-abstraction — [Advanced] — ERC-4337 and EIP-7702, sponsored gas, session keys, social recovery — and an honest status report
Related
- web3 curriculum map
- JS/TS for web3 — viem, wagmi, the code
- frontend — the 90% of a dapp that’s ordinary web development
- smart contracts — the other side of the wire
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering