New: Roadmaps ordered paths through our cheat sheets and flashcards, so you always know what to study next.
Explore themSee what's new on GitHubFrom how a block gets mined to a smart contract that survives an audit and ships.
A 12-step learning path. Follow it in order, or jump to what you need.
For anyone who wants to build on Web3 rather than just trade on it: you'll start from how blocks, consensus, and wallets actually work, then write, test, and secure smart contracts, and finish by shipping a real dApp with a working frontend. No prior experience needed, start from zero; plan on about 6 to 8 weeks at a few hours a week. This path does not cover general backend API design or web application security in the depth of backend-developer or web-security-essentials; it stays narrowly focused on the blockchain-specific slice, from Solidity to token standards to contract auditing. By the end you can write and test a Solidity smart contract, catch the exploits that have drained real protocols before they ship, and connect a web frontend to a live chain.
No prior experience needed. Start from zero.
Gives you the blocks-consensus-wallets mental model every later step assumes, and every table here maps to something you'll build hands-on soon.
Every contract repo you touch from here on lives in Git, and GitHub Actions is how teams gate deployments behind passing tests.
Hardhat scripts, ethers.js calls, and most contract tooling ahead all run in JavaScript, so this is the syntax you'll be typing constantly.
You can read a block explorer and reason about consensus, and the Git and JavaScript habits from steps 2 and 3 are the ones every contract tool ahead assumes. Next up: writing your first smart contract.
Finish this section to unlock.
+100 XP
This is where the reading from step 1 turns into code you can break: state variables persist forever and gas costs bite for real. Expect to come back to storage layout and gas patterns more than once before they click.
Takes the Solidity from step 4 off the page: Hardhat and Foundry compile, run a local chain, and deploy your contract so you can actually see it work.
A contract you deploy is immutable, so the unit and fuzz tests you write here are the only real safety net before step 7's security pass.
Reentrancy, overflow, and front-running have drained real money from contracts that passed every test in step 6; this is where you start thinking like the attacker, and that habit never fully switches off.
You can write, test, and defend a smart contract against the reentrancy and overflow bugs that have drained real protocols; a few minutes of due flashcards keeps steps 1 through 6 fresh while you build on them next. Next up: token standards and a frontend that talks to your contract.
Finish this section to unlock.
+100 XP
Take this if you want the elliptic-curve math and hashing internals behind the signatures step 7 told you to protect; the required path works fine without it.
Builds directly on the DeFi Primitives table from step 1: now you implement the ERC-20, ERC-721, and lending-protocol patterns that table only sketched.
Nobody uses a contract through Remix in production: ethers.js and wallet connection are how the token contracts from step 9 actually reach a user's browser.
Aim for this if L2-native or protocol-infrastructure roles interest you: rollups and bridges are where most scaling jobs actually live, and step 12's deploy checklist assumes you've already picked a chain.
Pulls every earlier step onto a real network: the contract from step 4, the tests from step 6, the security pass from step 7, and the frontend from step 10 all have to work together once real users and real funds show up.
You can take a smart contract from a blank Solidity file to a tested, audited, deployed dApp with a working frontend, the whole loop this badge certifies.
Finish this section to unlock.
+100 XP
Finish every required step, at least 70% of them genuinely done (not skipped), to earn this badge and 500 XP.