Skip to content

Cryptocurrency and Blockchain Fundamentals - Learning Plan

Target Audience: Tech professionals entering crypto/blockchain domain (engineers, SREs, infrastructure)
Prerequisites: General tech background, no prior finance or crypto knowledge required
Estimated Time: 6-8 weeks for domain literacy, 12-16 weeks for deeper technical understanding

Overview

This learning plan teaches cryptocurrency and blockchain technology fundamentals from a tech-oriented perspective. The goal is to enable you to: - Understand blockchain fundamentals (Bitcoin, Ethereum) - Grasp crypto exchange architecture (how platforms like Kraken operate) - Comprehend smart contract and DeFi concepts - Navigate Web3 infrastructure and tooling - Address security and custody topics

Why Relevant: - Crypto/Web3 infrastructure roles (e.g., Kraken Senior AI Compute Infrastructure Engineer) - Blockchain protocol development - DeFi platform engineering - Domain knowledge for tech interviews

Important Disclaimer: This is NOT investment advice. The goal is technical understanding, not trading strategy.

10 Modules: From Crypto Fundamentals to Web3 Infrastructure

Module 1: Bitcoin Basics - The First Blockchain

Goal: Understand how Bitcoin works, what blockchain is, and why it's a significant innovation.

Content:

  1. What is Bitcoin?
  2. Digital currency concept (peer-to-peer electronic cash)
  3. Satoshi Nakamoto whitepaper (2008) - MANDATORY reading
  4. Problem: Double-spending prevention in decentralized systems
  5. Source: Bitcoin whitepaper (9 pages, technical but readable)

  6. Link: https://bitcoin.org/bitcoin.pdf

  7. Blockchain data structure

  8. Blocks (transaction groups)
  9. Chain (cryptographic hash linking)
  10. Immutability (modification = entire chain recalculation)
  11. Source: Mastering Bitcoin (Andreas Antonopoulos, Chapter 7)

  12. Link: https://github.com/bitcoinbook/bitcoinbook

  13. Proof of Work (PoW) consensus

  14. Mining concept (nonce search, SHA-256 hash puzzle)
  15. Difficulty adjustment (every 2016 blocks, ~2 weeks)
  16. Economic security model (51% attack cost)
  17. Energy consumption debate

  18. Source: Bitcoin whitepaper Section 4 (Proof-of-Work)

  19. UTXO model (Unspent Transaction Output)

  20. Not "account balance" but "unspent outputs"
  21. Transactions = inputs (previous UTXOs) + outputs (new UTXOs)
  22. Change addresses (change mechanism)
  23. Source: Mastering Bitcoin, Chapter 6 (Transactions)

Practical Exercise (5-7 days): - Read the Bitcoin whitepaper (9 pages, 1-2 hours) - Explore Bitcoin block explorer (blockchain.com, blockchair.com) - Trace a transaction: inputs → outputs → confirmations - Optional: Run Bitcoin Core node (testnet, not mainnet!) - Blog post: "Bitcoin UTXO model explained with example"

Checkpoint: - Can you explain what blockchain is and why it's immutable? - Do you understand Proof of Work consensus (why mining is necessary)? - Are you familiar with the UTXO model (vs. account-based systems)?

Module 2: Ethereum and Smart Contracts

Goal: Understand Ethereum's difference from Bitcoin (programmable blockchain).

Content:

  1. Ethereum core concept
  2. "World Computer" vision (decentralized computation platform)
  3. Vitalik Buterin whitepaper (2013)
  4. Ethereum vs. Bitcoin: Turing-complete scripting
  5. Source: Ethereum whitepaper

  6. Link: https://ethereum.org/en/whitepaper/

  7. Ethereum Virtual Machine (EVM)

  8. Bytecode execution environment
  9. Gas concept (computation metering, spam prevention)
  10. Gas price vs. Gas limit (transaction fee calculation)
  11. Source: Ethereum Yellow Paper (technical spec, difficult reading)

  12. Easier alternative: "Mastering Ethereum" (Antonopoulos + Wood)

  13. Smart Contracts basics

  14. Solidity language (JavaScript-like syntax)
  15. Contract deployment (bytecode on-chain)
  16. Function calls (state-changing vs. view functions)
  17. Events and logs (off-chain monitoring)
  18. Source: Solidity documentation

  19. Link: https://docs.soliditylang.org/

  20. Account model (vs. Bitcoin UTXO)

  21. Externally Owned Accounts (EOA) - user wallets
  22. Contract Accounts - smart contract code
  23. State storage (account balance, nonce, contract storage)
  24. Source: Mastering Ethereum, Chapter 7 (Smart Contracts)

Practical Exercise (7-10 days): - Deploy simple smart contract (testnet: Sepolia or Goerli) - Write basic Solidity contract (e.g., simple storage, counter) - Interact with contract via Remix IDE (browser-based Solidity IDE) - Explore Etherscan (Ethereum block explorer, contract verification) - Blog post: "First smart contract deployment - learning notes"

Checkpoint: - Do you understand Ethereum's "world computer" concept? - Are you familiar with the Gas mechanism (why it's needed, how it's calculated)? - Have you deployed a simple smart contract (testnet)?

Module 3: Cryptocurrency Exchanges - Centralized (CEX) Architecture

Goal: Understand how centralized exchanges (Kraken, Coinbase, Binance) operate.

Content:

  1. Exchange core functions
  2. Order book (bid/ask matching)
  3. Trading engine (high-performance order matching)
  4. Wallet custody (hot wallet vs. cold wallet)
  5. Fiat on/off ramps (KYC/AML compliance)
  6. Source type: Industry blog posts (Kraken, Coinbase engineering blogs)

  7. Uncertainty: Internal architecture is proprietary, public info limited

  8. Hot vs. Cold Wallets

  9. Hot wallet: Online, fast withdrawals (operational liquidity)
  10. Cold wallet: Offline, multisig, air-gapped (long-term storage, security)
  11. Risk trade-off: Convenience vs. Security
  12. Source: Kraken Security Practices blog

  13. Link: https://blog.kraken.com/product/security

  14. Order matching engine

  15. Latency requirements (microseconds matter)
  16. Matching algorithms (price-time priority)
  17. Market orders vs. Limit orders
  18. Order book depth (liquidity indicator)

  19. Source: Coinbase engineering blog (trading infrastructure)

  20. Regulatory compliance

  21. KYC (Know Your Customer) - identity verification
  22. AML (Anti-Money Laundering) - transaction monitoring
  23. Jurisdiction-specific regulations (US, EU, Asia differences)
  24. Source: Regulatory frameworks overview (not deep legal analysis)

Practical Exercise (5-7 days): - Create Kraken account (use your Nexo experience as baseline) - Explore Kraken API documentation (REST, WebSocket) - Paper trading (simulate trades, observe order book) - Compare Kraken vs. Coinbase vs. Binance feature sets - Blog post: "Centralized crypto exchange architecture overview"

Checkpoint: - Do you understand the hot/cold wallet trade-off? - Are you familiar with the order matching engine (price-time priority)? - Can you distinguish CEX vs. DEX (latter covered in Module 5)?

Module 4: Consensus Mechanisms - PoW vs. PoS

Goal: Understand different consensus algorithms and their trade-offs.

Content:

  1. Proof of Work (PoW) - deeper dive
  2. Hash rate and network security
  3. Mining pools (centralization concern)
  4. ASIC resistance (Ethereum pre-merge, Monero)
  5. Energy consumption critique

  6. Source: Bitcoin mining overview (Bitcoin Wiki)

  7. Proof of Stake (PoS) - Ethereum Merge

  8. Validators (stake 32 ETH)
  9. Slashing (penalty for malicious behavior)
  10. Energy efficiency (99.95% reduction vs. PoW)
  11. Finality (vs. probabilistic finality in PoW)
  12. Source: Ethereum Proof-of-Stake documentation

  13. Link: https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/

  14. Other consensus mechanisms

  15. Delegated Proof of Stake (DPoS) - EOS, Tron
  16. Proof of Authority (PoA) - private/consortium chains
  17. Byzantine Fault Tolerance (BFT) variants

  18. Source: Consensus algorithm comparison papers (research-heavy)

  19. Consensus security assumptions

  20. 51% attack (PoW)
  21. Nothing-at-stake problem (PoS)
  22. Long-range attacks (PoS)
  23. Economic security models
  24. Source: Vitalik Buterin blog posts on PoS security

Practical Exercise (5-7 days): - Compare Bitcoin (PoW) vs. Ethereum (PoS) block explorers - Calculate mining profitability (Bitcoin mining calculator online) - Understand Ethereum staking (not doing it, just research) - Read Vitalik's "A Proof of Stake Design Philosophy" - Blog post: "PoW vs. PoS trade-offs - technical comparison"

Checkpoint: - Can you explain the PoW vs. PoS security model difference? - Do you understand the significance of the Ethereum Merge (energy, finality)? - Are you aware of consensus mechanism trade-offs?

Module 5: Decentralized Finance (DeFi) Basics

Goal: Understand DeFi protocols (decentralized exchanges, lending, liquidity pools).

Content:

  1. What is DeFi?
  2. Decentralized Finance concept (no intermediaries)
  3. Smart contract-based financial primitives
  4. Composability ("money legos")
  5. Risks: smart contract bugs, oracle failures
  6. Source: DeFi Pulse (DeFi protocol aggregator)

  7. Link: https://defipulse.com/

  8. Automated Market Makers (AMM) - Uniswap

  9. Liquidity pools (x * y = k constant product formula)
  10. No order book (vs. CEX)
  11. Impermanent loss (liquidity provider risk)
  12. Slippage (large trades move price)
  13. Source: Uniswap V2 whitepaper

  14. Link: https://uniswap.org/whitepaper.pdf

  15. Lending protocols - Aave, Compound

  16. Collateralized lending (over-collateralization required)
  17. Interest rates (algorithmically determined by supply/demand)
  18. Liquidation (if collateral value drops below threshold)
  19. Flash loans (uncollateralized loans within single transaction)
  20. Source: Aave documentation

  21. Link: https://docs.aave.com/

  22. Stablecoins

  23. USDC, USDT (fiat-backed, centralized)
  24. DAI (crypto-collateralized, decentralized)
  25. Algorithmic stablecoins (UST collapse case study)
  26. Source: Stablecoin comparison analysis (Circle, MakerDAO docs)

Practical Exercise (7-10 days): - Explore Uniswap interface (testnet or mainnet view-only) - Calculate impermanent loss scenario (spreadsheet exercise) - Read Uniswap V2 whitepaper (technical, ~20 pages) - Understand Aave liquidation mechanics (docs + examples) - Blog post: "DeFi AMM vs. CEX order book - architecture comparison"

Checkpoint: - Do you understand how AMM works (constant product formula)? - Are you familiar with the impermanent loss concept? - Can you distinguish fiat-backed vs. crypto-collateralized stablecoins?

Module 6: Web3 and Decentralized Applications (dApps)

Goal: Understand Web3 stack (frontend + blockchain backend).

Content:

  1. Web3 stack overview
  2. Frontend (React, Vue - same as Web2)
  3. Wallet integration (MetaMask, WalletConnect)
  4. Smart contract interaction (ethers.js, web3.js libraries)
  5. Decentralized storage (IPFS, Arweave)
  6. Source: Web3 developer roadmap

  7. Link: https://roadmap.sh/blockchain

  8. Ethereum JSON-RPC API

  9. Node providers (Infura, Alchemy, QuickNode)
  10. RPC methods (eth_call, eth_sendTransaction, eth_getBalance)
  11. WebSocket subscriptions (real-time events)
  12. Source: Ethereum JSON-RPC specification

  13. Link: https://ethereum.org/en/developers/docs/apis/json-rpc/

  14. Wallet integration (MetaMask)

  15. Browser extension wallet
  16. Transaction signing (user approval required)
  17. Network switching (Mainnet, testnet, L2s)
  18. Source: MetaMask developer documentation

  19. Link: https://docs.metamask.io/

  20. IPFS (InterPlanetary File System)

  21. Content-addressed storage (hash-based addressing)
  22. Decentralized vs. centralized storage trade-offs
  23. NFT metadata storage (why IPFS for images)
  24. Source: IPFS documentation
  25. Link: https://docs.ipfs.tech/

Practical Exercise (7-10 days): - Build simple dApp (React + ethers.js + smart contract) - Connect MetaMask to dApp (testnet) - Read smart contract state (view function call) - Send transaction (state-changing function, testnet ETH) - Upload file to IPFS (via Pinata or web interface) - Blog post: "First Web3 dApp - wallet integration notes"

Checkpoint: - Have you deployed a simple dApp (frontend + smart contract interaction)? - Do you understand wallet integration (signing, approval flow)? - Are you familiar with the IPFS use case (NFT metadata, decentralized storage)?

Module 7: Layer 2 Scaling Solutions

Goal: Understand Ethereum scalability problems and L2 solutions.

Content:

  1. Ethereum scalability trilemma
  2. Decentralization vs. Security vs. Scalability
  3. Current Ethereum limitations (~15 TPS, high gas fees)
  4. Vitalik's roadmap (rollup-centric future)
  5. Source: Vitalik Buterin blog - "The Limits to Blockchain Scalability"

  6. Link: https://vitalik.eth.limo/

  7. Optimistic Rollups (Optimism, Arbitrum)

  8. Execution off-chain, data on-chain (data availability)
  9. Fraud proofs (7-day challenge period)
  10. EVM compatibility (easy dApp migration)
  11. Source: Optimism documentation

  12. Link: https://community.optimism.io/docs/

  13. Zero-Knowledge Rollups (zkSync, StarkNet)

  14. ZK proofs (validity proofs, instant finality)
  15. Higher computational overhead (proof generation)
  16. Future scalability (zk-SNARKs, zk-STARKs)
  17. Source: zkSync documentation

  18. Link: https://docs.zksync.io/

  19. State channels, Plasma, Sidechains

  20. State channels (Lightning Network for Bitcoin)
  21. Plasma (deprecated Ethereum scaling approach)
  22. Sidechains (Polygon PoS - not a "true" L2)
  23. Source: Ethereum L2 comparison
  24. Link: https://l2beat.com/

Practical Exercise (5-7 days): - Bridge funds to Optimism or Arbitrum (testnet) - Deploy smart contract on L2 (compare gas costs vs. mainnet) - Explore L2Beat (L2 comparison, TVL, risk analysis) - Read Vitalik's "An Incomplete Guide to Rollups" - Blog post: "Optimistic vs. ZK rollups - trade-offs"

Checkpoint: - Do you understand the scalability trilemma? - Can you distinguish Optimistic vs. ZK rollups? - Have you deployed a smart contract to L2 (testnet)?

Module 8: Cryptocurrency Security and Custody

Goal: Understand private key management, wallet security, custody solutions.

Content:

  1. Private key cryptography basics
  2. ECDSA (Elliptic Curve Digital Signature Algorithm)
  3. Public/private key pair (Bitcoin, Ethereum same curve: secp256k1)
  4. Seed phrases (BIP-39 mnemonic, 12-24 words)
  5. Derivation paths (BIP-44, HD wallets)

  6. Source: Mastering Bitcoin, Chapter 4 (Keys, Addresses)

  7. Wallet types

  8. Software wallets (MetaMask, Trust Wallet)
  9. Hardware wallets (Ledger, Trezor)
  10. Paper wallets (cold storage, airgapped)
  11. Multisig wallets (Gnosis Safe)

  12. Source: Wallet security best practices (Bitcoin Wiki)

  13. Custody solutions (Exchange context)

  14. Self-custody (not your keys, not your coins)
  15. Custodial services (Coinbase Custody, Fireblocks)
  16. Institutional custody (regulatory requirements)

  17. Source: Kraken custody blog posts

  18. Common attack vectors

  19. Phishing (fake websites, social engineering)
  20. Clipboard malware (address replacement)
  21. SIM swapping (2FA bypass)
  22. Smart contract exploits (reentrancy, flash loan attacks)
  23. Source: Rekt News (DeFi exploit database)
  24. Link: https://rekt.news/

Practical Exercise (5-7 days): - Generate Bitcoin/Ethereum address offline (Python script or CLI tool) - Restore wallet from seed phrase (testnet, not mainnet!) - Research hardware wallet setup (don't buy yet, just understand workflow) - Read Rekt News top 5 exploits (case studies) - Blog post: "Crypto security fundamentals - key takeaways"

Checkpoint: - Do you understand private key → public key → address derivation? - Are you aware of hot/cold/multisig wallet trade-offs? - Can you generate an address from seed phrase (practical, but testnet!)?

Module 9: Blockchain Infrastructure and Node Operation

Goal: Understand blockchain node operation, infrastructure requirements (SRE/infra perspective).

Content:

  1. Full node vs. Light client
  2. Full node (complete blockchain, validation)
  3. Light client (SPV - Simplified Payment Verification)
  4. Archive node (complete historical state)
  5. Source: Bitcoin Core documentation

  6. Link: https://bitcoin.org/en/full-node

  7. Ethereum node clients

  8. Execution clients (Geth, Nethermind, Besu)
  9. Consensus clients (Prysm, Lighthouse, Teku)
  10. Post-merge architecture (execution + consensus)
  11. Source: Ethereum node setup guide

  12. Link: https://ethereum.org/en/developers/docs/nodes-and-clients/

  13. Node infrastructure requirements

  14. Storage (Bitcoin ~500GB, Ethereum ~1TB+ for archive node)
  15. Network (P2P gossip, peer discovery)
  16. Sync time (initial sync days/weeks)
  17. Hardware recommendations (SSD required, RAM)

  18. Source: Geth hardware requirements documentation

  19. RPC node providers (Infura, Alchemy)

  20. Managed node infrastructure
  21. API rate limits, pricing
  22. Geographic distribution (latency considerations)
  23. Source: Infura, Alchemy product documentation

Practical Exercise (7-10 days): - Run Bitcoin Core (testnet) - sync, observe logs - Run Geth (Ethereum testnet) - execution client - Query local node via JSON-RPC (curl or Postman) - Monitor node metrics (disk usage, peer count, sync status) - Blog post: "Running Ethereum node - infrastructure notes"

Checkpoint: - Have you run a Bitcoin or Ethereum node (testnet)? - Do you understand the full node vs. light client trade-off? - Are you aware of storage/network requirements?

Goal: Emerging topics, industry direction, career-relevant trends.

Content:

  1. Maximal Extractable Value (MEV)
  2. Front-running, sandwich attacks
  3. Flashbots (MEV mitigation)
  4. Block builder separation (PBS - Proposer-Builder Separation)
  5. Source: Flashbots documentation

  6. Link: https://docs.flashbots.net/

  7. Cross-chain bridges

  8. Wrapped tokens (WBTC, wrapped ETH on other chains)
  9. Bridge security risks (Ronin, Wormhole exploits)
  10. Interoperability protocols (Cosmos IBC, Polkadot)

  11. Source: Bridge exploit case studies (Rekt News)

  12. Ethereum roadmap (The Surge, The Scourge, etc.)

  13. EIP-4844 (Proto-Danksharding, blob transactions)
  14. Account abstraction (ERC-4337)
  15. Verkle trees (state tree optimization)
  16. Source: Ethereum roadmap

  17. Link: https://ethereum.org/en/roadmap/

  18. Industry career paths

  19. Smart contract developer (Solidity, Rust for Solana)
  20. Protocol engineer (core blockchain development)
  21. DeFi engineer (protocol design, security)
  22. Infrastructure/DevOps (node operation, indexers, RPCs)
  23. Source: Crypto job boards (Crypto Jobs List, Web3 Careers)

Practical Exercise (5-7 days): - Read MEV explanation (Flashbots docs) - Explore bridge transaction on block explorer (e.g., Ethereum → Polygon) - Read Ethereum roadmap overview (Vitalik's updates) - Browse crypto job postings (identify skill requirements) - Blog post: "Crypto industry trends - 2026 landscape"

Checkpoint: - Do you understand the MEV problem (and Flashbots solution)? - Are you aware of cross-chain bridge risks? - Can you identify main themes in Ethereum roadmap (scalability, UX, security)?

10 Practices: Practical Skill Development

Practice 1: Daily Crypto News Reading

  • What: Daily 15 min crypto news (CoinDesk, The Block, Decrypt)
  • Why: Industry awareness, trend spotting
  • Time: 15 min/day
  • Platform: Twitter (crypto accounts), Reddit (r/CryptoCurrency, r/ethereum)

Practice 2: Weekly On-Chain Analysis

  • What: Weekly explore an interesting transaction (Etherscan, Blockchain.com)
  • Why: On-chain data reading practice
  • Time: 30 min/week
  • Tool: Etherscan, Dune Analytics

Practice 3: Smart Contract Reading

  • What: Read 1-2 smart contract source codes weekly (verified contracts on Etherscan)
  • Why: Solidity pattern recognition
  • Time: 1-2 hours/week
  • Platform: Etherscan verified contracts, OpenZeppelin library

Practice 4: DeFi Protocol Monitoring

  • What: Follow 2-3 DeFi protocols (TVL, yield changes, governance votes)
  • Why: Understand protocol dynamics
  • Time: 30 min/week
  • Platform: DeFi Pulse, DefiLlama

Practice 5: Crypto Twitter Engagement

  • What: Follow key voices (Vitalik, developers, researchers)
  • Why: Direct insights, early trend awareness
  • Time: 15-30 min/day
  • Platform: Twitter/X (crypto community very active here)

Practice 6: Weekly Research Paper

  • What: Read 1 crypto/blockchain research paper weekly
  • Why: Deep technical understanding, academic perspective
  • Time: 2-3 hours/week
  • Sources: arXiv (cs.CR crypto category), Stanford Blockchain Research

Practice 7: Testnet Experimentation

  • What: Deploy contracts, test dApps, experiment with L2s (testnet only!)
  • Why: Hands-on experience, no financial risk
  • Time: 2-4 hours/week
  • Platform: Sepolia testnet (Ethereum), Bitcoin testnet

Practice 8: Security Incident Reviews

  • What: Analyze 1 major exploit/hack per month (Rekt News, post-mortems)
  • Why: Learn from failures, security awareness
  • Time: 1-2 hours/month
  • Platform: Rekt News, PeckShield alerts

Practice 9: Crypto Podcast Listening

  • What: Weekly crypto podcast (Bankless, Epicenter, Unchained)
  • Why: Interviews with builders, diverse perspectives
  • Time: 1 hour/week
  • Platform: Spotify, Apple Podcasts

Practice 10: Blockchain Explorer Deep Dives

  • What: Explore a blockchain explorer feature in depth (contract interactions, internal txs, token transfers)
  • Why: On-chain forensics skill
  • Time: 1 hour/week
  • Tool: Etherscan advanced features, Blockchair

Source Hierarchy and Reliability

Primary Sources (Most Reliable)

  1. Bitcoin whitepaper (Satoshi Nakamoto, 2008)
  2. Ethereum whitepaper (Vitalik Buterin, 2013)
  3. Protocol documentation (Ethereum.org, Bitcoin.org)
  4. Academic research papers (arXiv, peer-reviewed crypto conferences)

Professional Analysis (High Reliability)

  1. Mastering Bitcoin / Mastering Ethereum (Andreas Antonopoulos)
  2. Vitalik Buterin blog (Ethereum Foundation research)
  3. Protocol engineering blogs (Flashbots, Uniswap, Aave)
  4. Security firms (Trail of Bits, OpenZeppelin audits)

Community Sources (Medium Reliability)

  1. Reddit (r/CryptoCurrency, r/ethereum - user discussions)
  2. Crypto Twitter (developers, researchers - verify credentials)
  3. YouTube (Finematics, Whiteboard Crypto - educational channels)
  4. Medium/Substack (individual researcher blogs)

Sources to Verify (Low Reliability)

  1. Marketing materials (project whitepapers with no code - vaporware risk)
  2. Influencer opinions (often paid promotions, conflicts of interest)
  3. Price prediction content (speculation, not technical learning)
  4. Anonymous sources (verify claims before trusting)

Potential Biases and Uncertainties

Technological Biases

  • Ethereum-centric: Content is Ethereum-heavy (largest smart contract platform)
  • Alternatives: Solana, Avalanche, Cosmos (different design trade-offs)
  • Bias: Ethereum community narratives may influence objectivity

Investment Biases

  • Disclaimer: This is NOT investment advice
  • Crypto volatility: Prices can drop 50-90%
  • Regulatory risk: Government regulations can change (SEC, EU MiCA)
  • Technology risk: Smart contract exploits, protocol failures

Learning Curve Uncertainties

  • 6-8 week estimate: Assumes daily 1-2 hours intensive study
  • Variance: Depends on individual background (coding experience, finance knowledge)
  • Reality check: Domain literacy 6-8 weeks, deep expertise 6-12 months

Practical Limitations

  • Testnet practice cost: Free, but mainnet interaction expensive (gas fees $10-100+)
  • Alternative: Paper exercises, simulations (no real transactions)
  • Trade-off: Cheaper, but less production-like experience

Source Freshness

  • Rapid change: 6-month-old crypto tutorial may be outdated
  • Mitigation: Always check documentation publish date
  • Best practice: Official docs > blog posts (docs maintained, blogs static)

Next Steps (Using This Learning Plan)

  1. Assess commitment:
  2. Do you have 6-8 weeks for basic level? (domain literacy)
  3. Do you have 12-16 weeks for deeper tech understanding? (protocol level)

  4. If NOT: Consider part-time schedule (2-3 months, daily 30-60 min)

  5. Start with Module 1:

  6. Bitcoin whitepaper is mandatory (9 pages)

  7. Don't skip ahead (fundamentals are critical)

  8. Track progress:

  9. Markdown checklist (checkbox after each module)

  10. Blog posts = public accountability

  11. Adjust as needed:

  12. If a module is too fast/slow → customize

  13. If a tech stack isn't relevant (e.g., Solana) → skip or replace

  14. Build portfolio in parallel:

  15. GitHub repo for every smart contract project
  16. Blog posts at every milestone
  17. Goal: After 3-6 months, "Crypto-literate engineer" profile