Where to start with Ethereum
A reading path for Ethereum once you've understood Bitcoin — history, mental model, then engineering.
Ethereum is harder to learn than Bitcoin because the surface area is larger and the culture changes faster. The same advice applies, just shifted up a level: read the history before the mechanics, and don't try to learn DeFi until the base layer makes sense.
Step 1 — Read the history
The Infinite Machine by Camila Russo is the only book-length account of Ethereum's founding that's actually well-reported. Read it for the people and the politics; the technical content is light by design. By the end you'll understand why the protocol is shaped the way it is — which matters more than memorizing opcodes.
Step 2 — Build a mental model
Bankless is the cleanest weekly source for Ethereum and broader crypto-economic news. Subscribe; skip the speculative episodes; the protocol updates and developer interviews are gold. If you want a more visual primer, Finematics explains DeFi protocols in seven-minute whiteboard videos — pair it with Bankless and you'll have the mental model in a few weeks.
Step 3 — Learn the engineering
Mastering Ethereum is the canonical reference. It's dated post-Merge — the proof-of-stake material is patched in rather than rewritten — but the chapters on the EVM, gas, accounts, and Solidity are still the best treatment in book form. Read it with a testnet open. Deploy something tiny. Break it. Read the error.
What to do after
Once Mastering Ethereum makes sense, the open questions are no longer in books — they're in protocol-design forums, EIP discussions, and L2 docs. The blog's role at that point is to point you at one or two essays a week, not to be your textbook.
If you want a faster on-ramp without giving up rigor, our 12 best resources to learn Bitcoin post has a parallel layout that works just as well for Ethereum once you swap in the Ethereum-specific picks. The same principle applies: read the history, watch a few good explainers, then build something small and break it on a testnet. Don't try to short-cut steps two and three by skimming Twitter threads — there's no substitute for actually deploying a contract and watching it fail in interesting ways.