Web3 & Smart Contract Security
Engineers moving into contract development, and teams preparing a protocol for audit and mainnet.
Length
10 weeks, part-time
Commitment
~7 hours per week
Cohort
12 live sessions, 20 seats
What this track assumes
Strong general engineering background. Solidity familiarity helps but is not required.
What you cover
8 modules
Each one is worked through live, then built on between sessions.
- 01Delivering software you cannot patch — moving iteration upstream
- 02Solidity and the EVM execution model, written defensively
- 03Stating invariants explicitly and checking them mechanically
- 04Fuzzing, property-based testing and mainnet forking with Foundry
- 05Vulnerability classes and adversarial review practice
- 06Upgradeability, timelocks and multisig topology as trust decisions
- 07Key management and operational security — where most real losses occur
- 08Audit preparation — scoping, freezing, documenting, triaging findings
You build it, then you defend it.
There is no exam and no pass for attendance. Some people do not pass first time.
The project
A contract system with a stated invariant set, an adversarial review of another cohort member’s code, and an audit-readiness pack defended to a panel.
Read first
Some of this is free
The knowledge library covers a good deal of the same ground. Start there, and pay us only once you have decided the reviewed version is worth it.
Audit Scheduling And The Code Freeze
An external audit is a scarce dependency with a lead time, not a stage gate. How to book it, scope it, prepare for it, survive the freeze, triage findings, and plan the re-review as cost rather than surprise.
Delivering Software You Cannot Patch
Continuous delivery assumes you can ship a fix. On-chain, you cannot, and a defect is a withdrawal of funds. The answer is not waterfall — it is moving iteration upstream and making the irreversible step as small as possible.
Smart Contract Security As A Delivery Practice
Security fails when it is an end-stage gate. How to make threat modelling, stated invariants, fuzzing, forking, static analysis and adversarial review part of the ordinary development loop, and where formal methods earn their cost.
The On-Chain Boundary
Deciding what genuinely belongs on-chain and what is there for narrative reasons. Cost, latency, privacy and immutability as the four axes, the trust that oracles reintroduce, and the ordinary software that makes up most of a working system.
Other tracks
The rest of the technical family
AI Foundations
6 weeks, part-time
People who already use these tools daily and want to build with them — analysts, product people, and engineers early in their careers.
AI-Native Delivery
5 weeks, part-time
Teams adopting AI-assisted engineering who want the throughput gain to survive contact with review and production.
AI Engineering
8 weeks, part-time
Engineers building LLM applications, retrieval systems and agents who need them to hold up in production.
Agentic Systems Engineering
7 weeks, part-time
Engineers building systems that act on their own, and the leads accountable for what those systems do unsupervised.
Physical AI
7 weeks, part-time
Engineers moving from software-only AI to systems that act in the world, where being confidently wrong has consequences you cannot undo.
Mobile Delivery
5 weeks, part-time
Mobile teams whose release cadence is set by store review rather than by their own decisions.
Take Web3 & Smart Contract Security.
6 weeks, 12 live sessions, 20 seats, priced by region from $450. Places in the first cohorts are arranged directly.