The briefing
From the reading room
Latest notes
-
Bitcoin mining: from candidate block to accepted history
-
Ethereum accounts: addresses, keys, contracts, and nonces
-
Ethereum gas: distinguish work, price, and spending caps
-
Ethereum finality: from a quick receipt to finalized settlement
-
Smart contracts: inspect the rules and the people who can change them
-
Token approvals: understand the permission before the swap
Continuing the conversation
-
Token supply: read minting, burning, vesting, and circulation separately
-
Token decimals: translate raw balances without changing value
-
Stablecoin mechanics: identify the route back to the target value
-
Stablecoin reserves: read the assets, liabilities, and access terms
-
DeFi collateral: calculate the buffer before borrowing
-
AMM liquidity: what a pool position actually owns
02 / Explore the complete library
The mechanism, explained
Go beyond the headline: understand how the moving parts fit together.
-
DEX slippage: distinguish the quote, price impact, and tolerance
Read minimum output and deadlines before a swap, and understand why a successful trade can disappoint.
-
Oracle design: examine where a protocol gets its facts
Evaluate data sources, update rules, freshness checks, and failure behavior in oracle-dependent applications.
-
Blockchain bridges: trace the claim on both sides
Understand lock-and-mint, liquidity routes, message verification, and why a familiar symbol can conceal a new asset.
-
Rollups: separate execution speed from settlement guarantees
Compare optimistic and validity-based rollups, including data publication, sequencers, upgrades, and exits.
Practical reading
Worked examples, verification steps and the limits of each tool.
-
Data availability: why a valid commitment is not enough
Separate correctness proofs, retrievable transaction data, and long-term history when evaluating modular networks.
-
Protocol governance: follow a proposal through to execution
Inspect voting power, quorum, timelocks, and administrative authority beyond a headline approval result.
-
Multisig wallets: a threshold is only the beginning
Design independent approvals, recovery, and transaction review for shared digital-asset control.
-
Wallet backups: test recovery before you need it
Plan for device loss, missing passphrases, incompatible recovery, and secure succession without exposing wallet secrets.
-
Crypto phishing: inspect the requested authority, not the urgency
Recognize malicious recovery requests, address substitution, and signatures that grant more than they appear to.
-
Transaction explorers: read evidence without overreading labels
Follow status, contract calls, logs, and balance changes while separating public facts from explorer interpretation.
Questions worth asking
Read the assumptions before drawing a conclusion.
-
Onchain metrics: define the observation before telling a story
Interpret active addresses, transfer value, fees, and locked assets without pretending they directly count people or demand.
-
Trading volume quality: inspect what was counted and where
Separate spot turnover, derivatives notional, liquidity depth, and suspicious patterns before comparing markets.
-
Market capitalization: useful arithmetic with important limits
Calculate circulating and diluted valuations while separating marginal price, supply estimates, liquidity, and token rights.
-
Crypto research sources: build a claim-to-evidence trail
Use documentation, code, governance records, and independent observations without confusing first-party claims with proof.
-
Protocol upgrades: distinguish proposal, release, activation, and migration
Follow network and contract changes through their actual lifecycle instead of treating an announcement as completed behavior.
-
Staking: separate validator rewards from the service wrapper
Compare direct operation, pooled participation, liquid claims, penalties, fees, and withdrawal dependencies.
MEV: understand how transaction ordering changes outcomes
Learn the differences between arbitrage, liquidation, and sandwich behavior, plus the limits of private transaction routes.
NFT metadata: separate token ownership from the file it references
Inspect contract identity, token URIs, content addressing, storage persistence, and the limits of ownership claims.