Home / BlockChain Development / Blockchain
Blockchain
Intermediate
v2.0.0
From distributed-systems theory to shipping production smart contracts and protocols.
Want to learn blockchain but don't know where to start? This easy-to-understand roadmap covers everything from basic coding to building real-world decentralized apps (dApps). Whether you are new to programming or an experienced coder, this step-by-step guide will help you master smart contracts, Web3 tools, and build a strong portfolio to land your dream job.
Your progress
0 / 71 topics
0 %
Saved in this browser. Clearing site data will reset it.
Topics in this roadmap
The interactive map needs JavaScript. Here is the full list.
Consensus Mechanisms (PoW vs PoS)
How a decentralized network agrees on one history without a central coordinator.
Proof of Work: miners compete to find a nonce satisfying a difficulty target. Security comes from the cost of computation, rewriting history means outracing the entire honest network.
Proof of Stake: validators lock capital instead of burning electricity, and lose it (slashing) if they misbehave.
Interview importance
Very high. Expect to compare finality, liveness, and the economic security of each model.
Hash Functions and Merkle Trees
SHA-256 (Bitcoin) and Keccak-256 (Ethereum) map arbitrary data to a fixed size output with preimage and collision resistance. Merkle trees use hashing recursively so a light client can verify one transaction belongs to a block without downloading the whole block.
Mini project: build a Proof of Work miner that finds a nonce producing a hash with N leading zeros, and measure time against difficulty.
UTXO vs Account Model
Bitcoin has no balances, only unspent transaction outputs consumed and recreated each transfer. Ethereum tracks a balance and nonce per account, closer to a traditional ledger and simpler for smart contracts to reason about.
Public Key Cryptography and Signatures
A private key signs, a public key verifies, and nobody but the key holder could have produced a valid signature. ECDSA (secp256k1) underpins Bitcoin and Ethereum; EdDSA (Ed25519) is faster and used by chains like Solana.
Network Architecture (P2P, Nodes)
Nodes gossip transactions and blocks to random peers, who forward again, spreading information exponentially without any single node knowing the whole network. Full nodes verify everything, light nodes trust proofs, validator nodes additionally participate in consensus and can be slashed.
Digital Signatures and Verification
A signature proves a message was authorised by a private key's holder, without revealing that key. Signature malleability, replay protection, and nonce reuse are the classic failure modes worth studying.
Node Types and P2P Discovery
Full nodes verify everything but keep only recent state. Archive nodes keep full history. Light nodes trust proofs instead of verifying directly. A new node finds its first peers through bootnodes, DNS seeds, or discovery protocols like Discv5.
SegWit, Taproot, Schnorr Signatures
SegWit fixed transaction malleability and added block capacity. Taproot and Schnorr signatures made multisig transactions indistinguishable from single-signer ones, improving both privacy and fee efficiency.
Lightning Network (Layer 2)
Payment channels let two parties transact off-chain near instantly, settling on Bitcoin only when the channel opens or closes. The routing network connecting channels is Bitcoin's primary answer to scaling.
Bitcoin Improvement Proposals (BIPs)
Bitcoin's formal process for proposing protocol changes, requiring broad consensus among node operators and miners rather than a single foundation's sign off.
Running a Bitcoin Node
Practical setup of Bitcoin Core and the initial block download, and what it actually means to independently verify the entire chain of history yourself rather than trusting someone else's node.
Proof of Stake and the Beacon Chain
The Merge replaced Ethereum's Proof of Work execution layer with a Proof of Stake consensus layer without changing application behaviour. 32 ETH stakes a validator slot; slashing punishes provable misbehaviour like equivocation.
Rollup-Centric Scaling Roadmap
Ethereum abandoned execution sharding in favour of a rollup-centric roadmap: keep the base layer simple and secure, push execution scaling to Layer 2, and scale data availability instead.
Gas, Fees, and EIP-1559
EIP-1559 replaced first-price fee auctions with a base fee that adjusts per block and gets burned, plus an optional tip to the validator, making fees far more predictable than the old auction model.
Ethereum JSON-RPC API
The standard interface every client (Geth, Reth, and others) exposes for reading chain state and broadcasting transactions. Every wallet and dApp talks to a node through this API.
Liquid Staking (Lido, Rocket Pool)
Lets users stake less than 32 ETH and receive a liquid token (stETH, rETH) representing their position, which can then be used elsewhere in DeFi. This liquidity is also what makes restaking possible.
Foundry and Hardhat
Foundry, written in Rust, tests in Solidity itself and is now the industry default. Hardhat uses JavaScript/TypeScript and has a larger plugin ecosystem.
Foundry Book
OpenZeppelin and Token Standards
Audited, reusable implementations of ERC-20, ERC-721, ERC-1155, access control, and upgradeable proxy patterns. Rebuilding these from scratch in production is rarely justified.
OpenZeppelin Docs
Upgradeability Patterns (Proxies)
Transparent, UUPS, and Beacon proxies each trade off gas cost, upgrade safety, and storage collision risk differently. UUPS is now generally preferred over the older transparent proxy.
Reentrancy Guard and CEI Pattern
The most notorious smart contract vulnerability. Caused the 2016 DAO hack, roughly 60 million dollars, and still appears in audits today.
The fix
Checks-Effects-Interactions: validate conditions, update state, then call external contracts, never the other order. OpenZeppelin's ReentrancyGuard modifier enforces this with a mutex flag.
Interview importance: Extremely high, frequently a live coding round.
Ethernaut CTF
Smart Contract Security and Auditing
Static analysis (Slither), symbolic execution (Mythril), and fuzzing (Echidna) catch different bug classes. Formal verification (Certora) proves correctness mathematically instead of testing a sample of inputs, the highest assurance level, and the most expensive to set up.
Slither
Damn Vulnerable DeFi
Inline Assembly and Yul
Writing EVM opcodes directly inside Solidity for maximum gas efficiency. Powerful and dangerous: assembly bypasses Solidity's type safety and bounds checking entirely, so every line deserves an audit-level review.
Diamond Standard (EIP-2535)
Splits a contract's logic across many facets sharing one storage layout, working around the 24KB contract size limit. Powerful for large protocols, notoriously easy to get storage layout wrong in.
Formal Verification and Certora
Mathematically proves a contract satisfies a specification for all possible inputs, rather than testing a sample of them. The highest assurance level available, and the most expensive to set up.
Audit Tools (Slither, Mythril, Echidna)
Static analysis (Slither), symbolic execution (Mythril), and fuzzing (Echidna) each catch a different class of bug. A serious audit uses several of these together, never just one.
Lending Protocols (Aave, Compound)
Overcollateralised lending where interest rates float with utilisation, and positions below the health threshold get liquidated by anyone willing to repay the debt for a discount on the collateral.
Stablecoins
Fiat-collateralised (USDC), crypto-collateralised (DAI), and algorithmic designs each trade peg stability against capital efficiency and censorship resistance differently.
MEV Supply Chain
The post-Merge block production pipeline where validators, builders, relays, and searchers coordinate via MEV-Boost in a Proposer-Builder Separated architecture.
Why it matters
MEV affects every Ethereum user. Searchers extract value through arbitrage, sandwiches, and liquidations; MEV-aware protocol design prevents that value being extracted at users' expense.
Interview importance: High for DeFi engineering and protocol design roles.
Flashbots, MEV-Boost, and PBS
MEV-Boost lets a validator outsource block building to specialised builders competing for the most valuable block, in a Proposer-Builder Separated architecture. This is now the default path most Ethereum blocks take.
Derivatives and Options (Synthetix, GMX, Opyn)
On-chain leveraged trading and options protocols recreate traditional finance instruments with on-chain collateral and, usually, an oracle-fed price feed instead of a centralised clearing house.
Real World Assets (RWAs) and Tokenization
Bringing traditional assets, treasuries, real estate, private credit, onto public chains as tokens, trading capital efficiency and composability against the legal complexity of enforcing off-chain ownership claims.
ZK Rollups (zkSync, Starknet, Scroll)
Generates a validity proof for every batch of transactions, verified on Layer 1 cheaply. Withdrawals are fast since correctness is proven rather than assumed, but proof generation is computationally expensive.
Data Availability (Celestia, EigenDA)
Light nodes sample small random pieces of block data; if enough samples succeed, the whole block is probabilistically available without any single node downloading it in full. The core enabler of the modular blockchain thesis.
Celestia LazyLedger Paper
Fraud Proofs vs Validity Proofs
Optimistic rollups assume validity and only compute on a fraud proof challenge. ZK rollups prove validity upfront with a validity proof. This single design choice explains most of the UX and cost differences between the two rollup families.
Modular vs Monolithic Blockchains
A monolithic chain handles execution, consensus, and data availability itself. A modular chain outsources one or more of those to a specialised layer, trading simplicity for the ability to scale each piece independently.
LayerZero, Wormhole, CCIP
Chainlink Oracle Networks
Smart contracts cannot fetch external data themselves. An oracle network of independent nodes reports off-chain data on-chain, with an honest-majority assumption replacing a single trusted data source.
Chainlink Docs
IBC and Cosmos Interoperability
The Inter-Blockchain Communication protocol lets sovereign Cosmos SDK chains exchange verified messages directly, without a third-party bridge validator set, using light client proofs instead.
Chainlink VRF, Automation, and Functions
Beyond price feeds, Chainlink also provides verifiable randomness (VRF) for fair on-chain draws, Automation for scheduled contract calls, and Functions for arbitrary off-chain compute with an on-chain result.
ZK-EVMs and Circuits
A ZK-EVM proves Ethereum-equivalent execution inside a zero-knowledge circuit. Circom, Halo2, and Noir are the dominant circuit-writing languages, each with different tradeoffs between developer ergonomics and proving performance.
Circuits and R1CS
A zero-knowledge circuit expresses a computation as a Rank-1 Constraint System, a set of polynomial equality constraints the prover must satisfy. Every ZK language ultimately compiles down to something like this.
Trusted Setup Ceremonies
Some SNARK systems (Groth16) require a one-time trusted setup where secret randomness must be destroyed by at least one honest participant. PLONK and STARKs remove this requirement entirely, a major reason for their popularity.
Running Validators and Node Operations
Practical operation of consensus and execution clients, monitoring with Prometheus and Grafana, and the slashing risks that come with running infrastructure that stakes real capital.
Client Diversity and Its Risks
If one client implementation dominates and has a bug, the whole network can finalise an invalid state or split. Running a minority client such as Nethermind or Erigon is a public good, not just a personal preference.
Subgraph Indexing (The Graph)
Indexes blockchain events into a queryable GraphQL API, so a frontend never needs to scan the whole chain itself for historical data.
The Graph on GitHub
Distributed Validator Technology (DVT)
Splits a single validator key across multiple operators using threshold cryptography, so no single machine failing or being compromised can slash the whole stake.
ERC-4337 Account Abstraction
Introduces smart contract wallets with arbitrary verification logic and gas sponsorship, without any consensus layer change.
Why learn this
Wallet UX is the largest barrier to mainstream adoption. Account abstraction enables seedless recovery, gasless transactions via paymasters, and session keys.
Mini project: build a gasless NFT mint where a paymaster sponsors gas for users who connect with email or social login.
Interview importance: High for Web3 frontend and wallet infrastructure roles.
ERC-4337 Specification
Wallet Connections (RainbowKit, WalletConnect)
Standardised libraries handling the connection handshake between a dApp and dozens of different wallets, so developers do not reimplement this fragile integration surface themselves.
Session Keys and Paymasters
Session keys let a dApp sign a bounded set of actions on a user's behalf without repeated prompts, ideal for gaming. Paymasters let a project sponsor gas so users never need ETH in their wallet just to get started.
EigenLayer and Restaking
Lets ETH stakers secure additional services (AVSs) by opting into additional slashing conditions, extending Ethereum's pooled security to new middleware without each service bootstrapping its own validator set.
Common mistakes
Treating restaking as risk-free, slashing risks compound across every AVS opted into. Confusing EigenLayer with liquid staking, it is a separate layer built on top. Interview importance: Very high for protocol engineering roles, and rapidly becoming a differentiator.
EigenLayer Docs
DAOs and On-Chain Governance
Proposals, voting, and on-chain execution through frameworks like OpenZeppelin Governor. Quadratic and conviction voting attempt to fix plutocratic one-token one-vote systems, each with their own new failure modes.
Legal, Compliance, and Privacy
MiCA in the EU and the Travel Rule under FATF guidance are reshaping how exchanges and protocols must handle user data. The Howey Test still governs whether a token is a security in the United States. OFAC sanctions on Tornado Cash addresses set the precedent for smart-contract level sanctions enforcement.
EigenLayer and Restaking
Lets ETH stakers secure additional services (AVSs) by opting into additional slashing conditions, extending Ethereum's pooled security to new middleware without each service bootstrapping its own validator set.
Common mistakes
Treating restaking as risk-free, slashing risks compound across every AVS opted into. Confusing EigenLayer with liquid staking, it is a separate layer built on top. Interview importance: Very high for protocol engineering roles.
EigenLayer Docs
Liquid Restaking Tokens (LRTs)
Wraps a restaked position into a liquid, tradeable token, letting a user restake and still use that capital elsewhere in DeFi, at the cost of stacking another layer of smart contract and slashing risk on top.
veTokenomics and Gauge Voting
Vote-escrowed tokenomics, pioneered by Curve, locks tokens for a chosen duration in exchange for voting weight over which pools receive emissions, aligning long-term holders with protocol direction.
Intent-Based Architectures (CowSwap, UniswapX)
Instead of specifying an exact execution path, users declare a desired outcome and competing solvers find the best way to fulfil it, often producing better prices than a naive direct swap.
Smart Contract Engineer — $120K to $250K
Solidity, Foundry/Hardhat, OpenZeppelin, EVM internals, gas optimisation, and security patterns. Portfolio value comes from production projects with test suites and audit contest placements on Code4rena or Sherlock.
Protocol Engineer — $150K to $300K
Rust or Go, distributed systems theory, P2P networking, and consensus specifications. Builds blockchain clients, rollup infrastructure, and L1/L2 consensus mechanisms.
Blockchain Security Auditor — $130K to $280K
Reviews contracts and protocol architecture for vulnerabilities, at audit firms, independently in contests, or in-house. Code4rena/Sherlock top-10 finishes matter far more than certifications.
What is Blockchain?
A distributed ledger that many independent parties can verify without trusting each other, made tamper evident by linking every block to the one before it with a cryptographic hash.
Why learn this
Forms the mental model that distinguishes blockchain from a conventional database and establishes the vocabulary for every topic that follows.
Common mistakes
Assuming data on-chain is encrypted, it is public by default. Confusing blockchain with cryptocurrency. Interview importance: High, nearly every interview starts here.
Bitcoin Whitepaper
Bitcoin Architecture and Scripting
['Bitcoin Script is deliberately non-Turing-complete, a stack based language with no loops, which is a security feature: no risk of a script that never terminates.']
Bitcoin Developer Docs
EVM Architecture and Gas
The EVM is a stack machine executing bytecode one opcode at a time, each with a fixed gas cost. EIP-1559 replaced first-price fee auctions with a base fee that adjusts per block and gets burned, plus an optional tip to the validator.
Ethereum Yellow Paper
Ethereum Developer Docs
Solidity Language Deep Dive
Comprehensive mastery of Solidity: value and reference types, storage vs memory vs calldata, function visibility, modifiers, inheritance, low-level calls (call, delegatecall, staticcall), and inline assembly (Yul) for gas optimisation.
Common mistakes
Confusing storage and memory, wasting gas. Using transfer/send for ETH, hitting the 2300 gas stipend limit. delegatecall to untrusted contracts, causing storage collisions.Interview importance: Extremely high, the primary technical screen for smart contract roles.
Solidity Documentation
Automated Market Makers (Uniswap)
Replaces an order book with a pricing formula. V2 uses the constant product curve x times y equals k. V3 added concentrated liquidity. V4 added hooks, letting developers inject custom logic at each pool lifecycle stage.
Uniswap V4 Core
Optimistic Rollups (Arbitrum, Optimism)
Assumes transactions are valid by default and only runs computation if someone submits a fraud proof during a challenge window, typically about seven days. Simple to build, but withdrawals are slow unless a liquidity provider fronts them.
Bridge Security Models
Most bridge hacks, historically the largest losses in the industry, come from trusting a small validator set to attest cross-chain state. Lock-mint, burn-mint, and atomic swap designs each carry different trust assumptions.
SNARKs vs STARKs
Cryptographic protocols letting a prover convince a verifier a statement is true without revealing the underlying information.
SNARKs (Groth16, PLONK) produce tiny proofs but usually need a trusted setup ceremony. STARKs produce larger proofs but need no trusted setup and are believed post-quantum secure.
Why learn this
ZK is the scaling and privacy endgame for blockchain. ZK engineers are among the highest paid specialists in the industry.
Mini project: build a ZK age-verification circuit in Circom proving you are over 18 without revealing your birthdate.
Circom
Zero Knowledge Podcast
Blockchain Clients (Geth, Reth)
If one client implementation dominates and has a bug, the whole network can finalise an invalid state or split. Running a minority client such as Nethermind or Erigon is a public good, not just a personal choice.
Reth on GitHub
Web3 Frontend (Wagmi, Viem)
Viem and Wagmi are the modern, TypeScript-native replacement for the older Ethers.js and Web3.js stack, offering smaller bundles and stricter typing.
Token Design and Incentive Mechanisms
Vesting schedules, emission curves, and governance token value accrual determine whether long-term holders and short-term speculators are aligned or working against each other.
