Track 72 hands-on activities, eight abilities, and 12 stage projects.
This course measures completion through work you produce.
This page shows progress through practical activities and which artifacts you can already share.
All checkmarks stay in your browser, with no uploads. Another device needs its own checks.
There are no accounts: your submitted work is the real Proof of Skill.
Each chapter ends with a checkbox. Check it after completing the activity; progress appears here.
Overall lab progress0 / 72
0 / 72
Mental ModelCan explain in your own words why a crypto system exists instead of repeating its feature list.
0 / 7
Protocol LiteracyCan explain the state, participants, incentives, and failure modes of a chain or protocol.
0 / 20
Financial LiteracyUnderstand liquidity, leverage, collateral, liquidation, yield, and balance sheets; when you see APY, ask where it comes from first.
0 / 21
Onchain LiteracyCan read wallets, transactions, contracts, holder distributions, and pools yourself without relying on others' conclusions.
0 / 16
ResearchCan give an evidence-based judgment on an unfamiliar project in 30 minutes and explain the uncertainties.
0 / 14
BuilderCan turn an on-chain idea into a deployable, verifiable product others can use.
0 / 38
AI LiteracyCan use AI to speed up research and development while detecting model errors and permission risks and knowing what not to delegate.
0 / 13
System ThinkingCan see participants, resources, rules, incentives, value, risks, power, narratives, and feedback loops together.
0 / 20
The eight abilities are derived from chapters. Course data identifies which abilities each chapter practices. Completing it advances those abilities. A stalled ability indicates you have been avoiding those chapters.
Activities are practice; stage projects are outputs others can open, run, and inspect. These matter when seeking jobs, collaborators, or Grants.
Non-Technical Crypto OS · Stage 1 · Why crypto emergedA breakdown of the first on-chain transaction from your own wallet, explaining each step from signing to finality.
Non-Technical Crypto OS · Stage 2 · Blockchain EconomyA comparison table of three chains: security, execution, state, latency, decentralization, and hardware requirements.
Non-Technical Crypto OS · Stage 3 · How crypto reinvents financeBreak down the sources of yield in a DeFi pool, with on-chain data screenshots and a risk checklist.
Non-Technical Crypto OS · Stage 4 · Tokens, markets, and researchA tokenomics analysis covering supply, unlocks, value capture, and dilution.
Non-Technical Crypto OS · Stage 5 · Crypto BusinessA 30-minute project brief: fill all thirteen cells of the Project Canvas and give a verdict.
Non-Technical Crypto OS · Stage 6 · AI × Crypto and the future on-chain economyAn agent permission design document: budget, allowlist, approval thresholds, and audit log.
Technical Crypto OS · Stage 1 · Blockchain Developer Mental ModelA command-line tool that reads blocks and accounts, parses a transaction, and prints state changes.
Technical Crypto OS · Stage 2 · Smart Contract EngineeringA fully tested token contract, deployed to testnet with source code verified in a block explorer.
Technical Crypto OS · Stage 3 · Full-stack Onchain ApplicationA full-stack dApp: connect a wallet, send transactions, index events, and refresh in real time.
Technical Crypto OS · Stage 4 · DeFi EngineeringA runnable AMM and router, with tests for slippage, fees, and liquidation.
Technical Crypto OS · Stage 5 · Infrastructure & SecurityA threat model and invariant checklist, with fuzzing tests and monitoring alerts.
Technical Crypto OS · Stage 6 · AI × Crypto EngineeringAn on-chain agent with a wallet, budget, strategy engine, and audit log.
See Capstone Projects for requirements. Publish completed work. Private work has little value in recruiting and collaboration and misses the opportunity for criticism, which can teach more than days of solitary reading.
This page is a checklist. Organize a portfolio yourself:
One repository, one README.
The first screen should explain what it is, how to run it, and your trade-offs. The third often best reveals ability and is most often omitted.
State each project's known problems.
This demonstrates both understanding of the system and care in distinguishing verified from unverified claims.
Research must trace to sources.
Make every conclusion traceable through a link and label unsupported claims unverified. See Staying Current with Crypto.
Engineering projects must run for someone else.
The first acceptance request is always a link to try. Even good code attracts little serious attention if the repository cannot run.
Prepare a 20-minute walkthrough.
Spend 15 minutes on design and five answering challenges. Responding to criticism matters more than presentation polish, a shared requirement across Career Tracks.