Money & networks
Ledgers, digital scarcity, peer-to-peer systems, Bitcoin’s history, and terminology.
Structured curriculum
Use these outlines to organize self-study or compare program topics. Suggested durations are planning estimates, not fixed schedules.
Course catalog
Filter by your current priority. Each path includes prerequisites, outcomes, modules, and explicit limitations.
Beginner · Suggested 4 weeksMoney, scarcity, proof of work, transactions, wallets, market structure, asset categories, and risk.
View modules ↓
Technical · Suggested 8–10 weeksAccounts, transactions, smart contracts, client integration, testing, permissions, and secure application design.
View modules ↓
Security · Suggested 3 weeksKeys, recovery phrases, custody models, hardware devices, multisig, phishing defense, and recovery drills.
View modules ↓
Beginner-plus · Suggested 5 weeksToken design, supply, liquidity, exchanges, stablecoins, custody, scams, research frameworks, and regulation context.
View modules ↓
Technical · Suggested 6 weeksThreat modeling, access controls, external calls, testing strategy, common vulnerabilities, review, and incident readiness.
View modules ↓
Career · Suggested 6 weeksRole mapping, durable skill foundations, portfolio planning, public proof of work, ethical communication, and interviews.
View modules ↓Path 01 · Foundation
Start with systems and safety before market interpretation. Learners can complete the research activities without buying any asset.
Ledgers, digital scarcity, peer-to-peer systems, Bitcoin’s history, and terminology.
Keys, addresses, signatures, UTXOs, fees, blocks, confirmations, and explorers.
Proof of work, difficulty, issuance, halvings, and the difference between scarcity and value.
Custodial and self-custody models, backups, hardware wallets, phishing, and test transfers.
Smart-contract chains, stablecoins, tokens, Layer 2 systems, bridges, and categories.
Volatility, liquidity, counterparty risk, scams, regulation context, and responsible decisions.
Path 02 · Technical
Build on a solid programming foundation. The exercises should use test environments and valueless test assets wherever possible.
Accounts, transactions, state, virtual machines, fees, signing, and confirmation semantics.
Functions, storage, permissions, events, tokens, testing, deployment, and upgrades.
Wallet connections, RPC access, transaction construction, error states, and user safety.
Threat modeling, external calls, access control, fuzzing, review notes, and monitoring.
Path 03 · Security
A practical route based on threat modeling, careful configuration, and tested recovery—not slogans.
Identify who controls keys, how transactions are approved, and where account recovery depends on a third party.
Design offline backups around theft, observation, physical damage, inheritance, and human error.
Check networks, addresses, amounts, fees, approvals, destination ownership, and test-transfer outcomes.
Use unique credentials, strong multifactor authentication, safe devices, and verified support channels.
Test low-value recovery and incident steps before relying on a setup for meaningful assets.
Path 04 · Research
Describe the problem, intended user, actual mechanism, and why a blockchain is necessary.
Review the trust model, validator distribution, code maturity, audit history, bridges, and admin permissions.
Examine supply, issuance, allocation, unlocks, incentives, fee demand, and concentration.
Assess liquidity, venue quality, custody, spreads, leverage, and counterparty dependencies.
Compare primary documentation, code, public data, independent analysis, and counterarguments.
Write risks, unknowns, disconfirming evidence, position limits, and reasons to take no action.
Its purpose is to improve research discipline and risk awareness. A well-researched asset can still lose most or all of its market value.
Path 05 · Career
Combine one durable professional discipline with enough protocol fluency to work responsibly in the field.
Compare engineering, security, data, product, research, policy, and operations.
Choose a foundation employers already value and practice it in a blockchain context.
Create reviewable work with documentation, limitations, sources, and security thinking.
Explain trade-offs, avoid hype, and prepare examples that show decisions and learning.
Course questions
The planner stores nothing externally and asks for no personal details.
No. They are curriculum outlines for education and planning unless a specific provider separately states and verifies accreditation.
No. Foundation and research work can be completed without buying assets. Technical exercises should use test networks and valueless test assets.
No. Learning can build knowledge and demonstrable skills, but it cannot guarantee employment, compensation, market performance, or profit.
Answer three non-personal questions and get a suggested starting curriculum on this device.