Curriculum overview
6 weeks of written lessons and code examples — no videos. You’ll read, code, debug,
and ship real things. Here's the high-level structure:
Week 1 — Ethereum internals
- What is Ethereum? Execution vs Consensus layers
- What are Blocks, Transactions and Mempools
- What are node providers(For example ChainStack) and how to use them
- What are Nodes and how they really work (Geth, Erigon, Anvil)
- Get Familiar with EVM Developer Tools
- Hands-on:
- Install Foundry
- Start Foundry Project: Run Anvil, Explore default accounts, decode with cast tool
- run clients, inspect state, debug real txs
Week 2 — Wallets, Smart contracts & the EVM
- Solidity basics: state vars, functions, modifiers, events
- ABI, calldata, storage, logs, gas, errors & reverts.
- Understand how Solidity compiles to opcodes.
- What are wallets
- What are wallet providers
- Hands-on:
- Generate local wallet
- Setup 3rd party wallet
- Write + test ERC-20 with Foundry
- Execute Transactions on the deployed contracts
Week 3 — Transactions deep-dive
- RLP serialization basics.
- Transaction structure, gas, fees, replay protection
- Transaction types:
- Legacy Transaction
- Access List Transaction (EIP-2930)
- Dynamic Fee Transaction (EIP-1559)
- Set-Code Transaction (EIP-7702)
- Hands-on:
- Build, sign and publish raw transactions in Go
- Send raw transactions to a local Anvil node
Week 4 — Messages & signing
- Off-chain Messages:
- What are off-chain messages
- Use cases of off-chain messages
- Personal Sign Messages + EIP-191
- SignTypedData Message + EIP-712 signing + verification.
- On-chain Transactions Vs Off-chain Messages
- Hands-on:
- Implement EIP-191 personal_sign + verify in Go
- Implement EIP-712 signTypedData + verify in Go
Week 5 — Batching, On-chain activity & monitoring
- Events, logs, topics, and internal calls.
- Tracing hidden transfers with
debug_trace*.
- Batching, multicall, and WebSocket subscriptions.
- Hands-on:
- Build small block explorer that indexes events + traces
- Build a transaction monitor that tracks tx status + internal calls
Week 6 — Mini DEX + real-time dashboard
- Build a simple AMM-style pool contract
- Index events into a backend + Postgres integration
- Expose REST endpoints + build a live dashboard
By the end, you’ll ship a real vertical slice: contracts, backend, monitoring, and UI.
Join the next cohort
$499
Early Priority Access - You’re getting a special discounted rate reserved only for early signers of the Bootcamp. Future cohorts will be priced higher as the program expands and new modules are added.
This bootcamp is fully hands-on: weekly written lessons, deep code examples,
two 40-minute live calls with me each week, and private text support whenever
you get stuck.
Complete your payment below:
You’re in the bootcamp 🎉
Your payment was received successfully. You’ll receive an email shortly with:
- Bootcamp start date & time
- Links to the written materials
- Calendar invites for the live calls
If you don’t see the email within 10–15 minutes, check spam or message me directly.
FAQ
What’s the format?
This is not a “watch 40 hours of videos and forget everything” course.
You get written lessons, code examples, and exercises you run locally.
Each week we meet for two private 40-minute live calls (Q&A, debugging, code review),
plus you can message me privately for help between sessions.
Who is this for?
Developers (backend, full-stack, or Web3) who want to
understand how the chain actually behaves in production — beyond tutorials
and toy contracts. You should already be comfortable with at least one
programming language.
What will I be able to do at the end?
You’ll know how to reason about nodes, RPC, transactions, calldata,
logs, traces, and monitoring. You’ll have built a small AMM-style DEX
with a real backend and dashboard — the same architecture patterns many
production Web3 products use.
Will there be recordings?
Live calls are recorded for you, but there is no big pre-recorded
“video course”. The core of the bootcamp is the written material,
code, and the feedback loop between what you build and what we debug together.