web3.path

PHASE 16 Specialize · ongoing

Research & Specialization

At this point you've shipped a production-grade dApp. The field is too big to master all of it — pick a lane that matches your taste, and go deep.

Goal — pick a specialization, commit to reading real papers/codebases, and make visible contributions.

1. The five honest lanes in 2026

LaneDay-to-dayBackground fit
DeFi protocol engineerMechanism design, Solidity, market mathBackend + trading / finance
Security / auditorBreak things for a livingAdversarial mindset, deep EVM
InfrastructureNodes, RPC, indexers, rollup stacksDistsys / SRE background
ZK engineerCircuits, proving systemsMath-curious, Rust/C
Wallet / account abstractionUX, EIP-4337, passkeys, key managementFrontend + security

2. DeFi track

3. Security / auditor track

4. Infrastructure track

5. ZK track

6. Wallet / account-abstraction track

7. Staying current — a low-noise diet

8. How to contribute to OSS (for real)

  1. Pick one repo you've used (e.g., ethers.js, foundry-rs, openzeppelin-contracts).
  2. Read the CONTRIBUTING.md. Fix a "good first issue".
  3. Write one good bug report per month — reproducible, minimal, with a PR if possible.
  4. Participate in governance forums where you're a user (Compound, Uniswap). Temperature-check proposals.

9. Reading list — the canonical 15

  1. Bitcoin whitepaper (Nakamoto, 2008)
  2. Ethereum Yellow Paper (Wood)
  3. "Ethereum is a Dark Forest" (Dan Robinson) — MEV origin story
  4. Uniswap v2 whitepaper
  5. Uniswap v3 whitepaper (concentrated liquidity)
  6. EIP-1559 (fee market)
  7. EIP-4844 (blob transactions)
  8. EIP-4337 (account abstraction)
  9. Optimism: Cannon & fault proof design docs
  10. zkSync Era Litepaper
  11. "An Incomplete Guide to Rollups" (Vitalik)
  12. "Flash Boys 2.0" (MEV paper, Daian et al.)
  13. Paradigm: "The Dark Forest Revisited" & MEV-Boost docs
  14. "SoK: Decentralized Finance" (Werner et al.)
  15. Danksharding & PBS design docs (ethresear.ch)

10. Final project — pick one

Capstone (choose one, ship publicly) Write a teardown post. Tweet it. Put it on your CV.

11. Parting principle

Web3 rewards people who can hold two ideas at once: (a) software engineering is the same everywhere — correctness, observability, tests — and (b) the adversary is real and well-funded. Most fixes come from (a). Most losses come from forgetting (b).
← Phase 15Back to Home