CRYPTO
ACADEMY
No wallet, no funds, no risk

Practice drills

Eight scenarios that rehearse the decisions this course describes, using fictional setups only.

01
Chapter 1

Build a control map from a fictional asset page

A fictional token page says the asset is decentralized, backed, and governed by its community. Your task is to turn the claims into questions that can be verified.

Tasks

  1. List who can issue, freeze, upgrade, or redeem the asset.
  2. Separate network properties from issuer or website promises.
  3. Write one piece of evidence you would need for each claim.

You are done when

  • Every control claim has an identified actor or an explicit unknown.
  • Marketing language is separated from observable permissions and records.
Use the fictional setup only. Do not buy an asset or connect a wallet for this drill.
Review the chapter
02
Chapter 2

Trace a public transaction without using a wallet

Choose a transaction hash already published in official network documentation and follow it through that network's explorer.

Tasks

  1. Identify status, block, sender, destination, value, and fee.
  2. State what the explorer proves and what it cannot prove about the people involved.
  3. Describe how the finality signal differs from a service's internal status label.

You are done when

  • The explorer matches the transaction's actual network.
  • The explanation distinguishes inclusion, finality, and identity.
Use only a public example from official documentation. Never paste a private key, recovery phrase, or private transaction record.
Review the chapter
03
Chapter 3

Threat-model a recovery plan using dummy words

Create a paper plan for a fictional wallet containing no real assets and a clearly fake phrase such as ALPHA–BRAVO–CHARLIE.

Tasks

  1. List theft, fire, water, loss, coercion, and inheritance failure paths.
  2. Choose separated storage roles and document who can use them.
  3. Write a rehearsal that proves recovery without exposing a real secret.

You are done when

  • The plan addresses both unauthorized access and accidental loss.
  • No real recovery material is digitized, shared, or entered anywhere.
Never use a real recovery phrase in an exercise, note app, screenshot, cloud document, or support chat.
Review the chapter
04
Chapter 4

Draft a transfer route before moving value

A fictional service offers the same asset on three networks with different withdrawal fees. The receiving service supports only one of them.

Tasks

  1. Record asset, network, destination format, minimum deposit, withdrawal fee, and expected arrival checks.
  2. Define a small test-transfer amount and a stop condition.
  3. Explain how you would reuse the verified route after the test arrives.

You are done when

  • The selected network is explicitly supported at both ends.
  • The plan has a pause point before any meaningful transfer.
Complete the worksheet without sending funds. Use it as a template only after independently verifying a real route.
Review the chapter
05
Chapter 5

Break an attacker's verification loop

A fictional support message says your wallet will be suspended in ten minutes and provides a verification link.

Tasks

  1. Mark the pressure, impersonation, link, and requested authority signals.
  2. Write an independent route to the provider that does not reuse the message.
  3. Create a containment checklist for the case where a signature was already made.

You are done when

  • Verification happens outside the sender's channel.
  • The response preserves evidence and does not pay a recovery stranger.
Do not open suspicious links, install files, connect a wallet, or test a request with an empty wallet.
Review the chapter
06
Chapter 6

Calculate execution from a fictional order book

A fictional order book offers 10 units at $10, 20 at $11, and 30 at $13. Compare a 10-unit buy with a 45-unit market buy.

Tasks

  1. Calculate the weighted average execution price for each order.
  2. Compare the result with the last quoted price.
  3. State how liquidity, order type, and fees affect the decision.

You are done when

  • The calculation uses available quantities at each price level.
  • The conclusion avoids treating a quoted price as guaranteed execution.
Use fictional numbers only. This is an execution exercise, not a recommendation to trade.
Review the chapter
07
Chapter 7

Map the dependencies behind a fictional yield

A fictional app advertises 18% yield on a bridged stablecoin deposited into an upgradeable lending market.

Tasks

  1. Identify who pays the return and whether incentives are temporary.
  2. Map issuer, reserve, bridge, oracle, contract, admin-key, liquidity, and user-interface dependencies.
  3. Write a failure scenario for three different layers.

You are done when

  • The advertised rate is separated from the source of return.
  • At least three independent failure paths and exit constraints are visible.
Do not connect to or deposit in a protocol for this drill. Analyze the fictional stack offline.
Review the chapter
08
Chapter 8

Create an evidence-ready event record

A fictional user buys an asset, moves it between personal wallets, swaps part of it, and pays a network fee.

Tasks

  1. Create one row per event with date, asset, quantity, value basis, fee, network, hash, and ownership note.
  2. Label which event might require jurisdiction-specific advice.
  3. Find the current primary authority you would consult and record its access date.

You are done when

  • Transfers are distinguishable from disposals without guessing later.
  • The legal or tax conclusion is deferred to a current authority and the user's jurisdiction.
Use fictional data. Do not upload personal wallet records or identifying transaction history.
Review the chapter