Go from a first testnet deploy to a tested, verified protocol you can defend line by line to a sceptical reviewer.
You can read a Solidity contract and mostly follow it, but you have never pushed one to a public network — and the gap is intimidating, because code on Ethereum is money and it is permanent. This course closes that gap by deploying on day one, then building up. You install Foundry, ship a contract to a local node and then to the Sepolia test network, and verify the source on Etherscan. From there you learn where every variable actually lives in storage and what each write costs in gas, write ERC-20 tokens and ERC-721 collections from scratch before reaching for OpenZeppelin, and use factories and upgradeable proxies without corrupting your storage layout. Foundry unit, fuzz, invariant, and fork tests back all of it. Later modules rebuild the primitives you already use: a constant-product automated market maker, an over-collateralized lending market with liquidations, and price oracles that survive a flash-loan attack. You finish by shipping a small protocol with a threat model you can defend.
Built by Lakshya Kumar
We grant free access case-by-case — students, career-switchers, builders on a tight budget. Sign in to send us a note.
Sign in to applyFinished the tasks? Take the prompt to your AI and get tested on it. We copy the prompt and open the app — just paste it in.
Find out where each variable lands in storage, pack two of them into one slot, and watch the gas bill actually drop.
Build ERC-20 and ERC-721 from scratch, then read OpenZeppelin and understand every line you would have copied.
Deploy many contracts from one factory, then swap an implementation without a storage collision wiping user balances.
Unit, fuzz, invariant, and mainnet-fork tests, plus gas snapshots that catch an expensive regression before you merge.
Derive the constant-product invariant, add liquidity shares and fees, then measure what a large trade costs the trader.
Build staking rewards, a utilization-based rate curve, and the health factor that decides when someone loses collateral.
Consume Chainlink feeds safely, use time-weighted averages, and aggregate sources so one bad price cannot drain the pool.
Checks-effects-interactions, access control, signature replay, and reading your own contract the way an auditor would.
Scope it, build it, test it four ways, deploy and verify it, then write the threat model that justifies every decision.
Complete all modules, then submit the required number of capstone projects. Each must earn a passing rating from an admin reviewer.
Build and deploy a small but real on-chain protocol (mini-DEX, lending market, or on-chain game) to a testnet. Include unit + fuzz tests, a README with threat model and known risks, and a deployment script. You should be able to defend every design decision in writing.
Build a production-quality ERC-20 token with a per-grantee vesting schedule supporting cliff and linear vest. Include full test coverage (Foundry), gas-optimized storage, role-based revocation by a governance multisig, and a deployment script that initializes a 100-grantee allocation. Verify on a public testnet and publish the verified source.
Paste this into any AI chat. Fill in the bracketed parts with your context — you'll get back a straight answer on whether this belongs on your plate.
I'm considering a "Solidity: Deploy, Write, Secure" course. It covers Foundry, the ERC standards (20/721/1155), proxy patterns, fuzz testing, AMMs, lending, oracles, gas optimization, and security — 100 challenges culminating in deploying a small auditable protocol to a testnet. My context: 1. Programming background: [e.g. "5 years of Python/TypeScript", "solid C/C++", "self-taught, 1 year in"] 2. Prior blockchain exposure: [e.g. "I know wallets + gas", "finished a Blockchain 101", "completely new — should I back up?"] 3. What I want after finishing: [e.g. "get hired as a smart-contract dev", "audit as a side gig", "ship a personal project", "understand DeFi I already use"] Answer: - Am I ready for this, or should I back up to a pure blockchain/Solidity-syntax course first? Be honest — don't cheerlead. - What's the realistic 12-month career arc for a solid graduate of this course in my geography? Salary range if you can, caveats if you can't. - Which of the 10 syllabus areas (Foundry / ERC / proxies / testing / AMMs / lending / oracles / gas / security / deploy) would be the single most valuable one to master first, in my case? - Smart-contract work has non-trivial risk (exploits ruin careers and people). Given my context, is that risk one I should embrace or avoid?
Implement an English auction contract supporting concurrent auctions, pull-payment refunds, anti-griefing minimum-increment rules, and a 5% fee router to a treasury. Add a frontend that watches auction events via viem. Test the bid-snipe edge case (last-minute bid extends the auction by 2 minutes).
Ship a UUPS-upgradeable contract with a storage-gap pattern, an initializer guard, role-based upgrade authorization, and a migration script that upgrades the implementation while keeping storage intact. Demonstrate at least one storage-layout regression caught by your tests.
Build a gas-efficient Merkle-airdrop contract: off-chain Merkle tree of 100k recipients, on-chain claim with proof verification, replay protection via bitmap, and a sunset window after which unclaimed tokens go to a treasury. Include the off-chain generator script and a tiny claim UI.
The entire course uses Foundry. Bookmark the testing and scripting chapters.