Start Here

The atlas is for software engineers who want to reason about blockchain protocols as replicated state machines with assets, authority, and adversarial ordering—not as investment products. The main laboratory is Solidity on the EVM, with other execution and interoperability models introduced when the contrast changes a design decision.

Working method

1. Read the phase overview and its branch indexes.
2. Before implementation, write actors, trust assumptions, state transitions, invariants, threats, and recovery behavior.
3. Build locally on Anvil with deterministic accounts and disposable keys.
4. Add example, fuzz, invariant, failure-injection, and adversarial tests in proportion to risk.
5. Use a maintained public testnet only after local evidence is reproducible.
6. Record deployment, source verification, roles, parameters, RPC assumptions, and rollback/containment steps.

Prerequisites

You should be comfortable with TypeScript, command-line tools, APIs, databases, and automated tests. The atlas rebuilds blockchain fundamentals, but does not reteach general programming. Low-level knowledge of bytes, hashing, processes, networking, and concurrency makes the execution and consensus sections much easier.

Safety boundary

All future code is educational and unaudited. Never paste a seed phrase, use production credentials, transact with real funds, deploy to mainnet, or treat a green test suite as an audit. Exploit labs stay on local forks or purpose-built test fixtures and explain the patch's limits.

Next: Must Know and Phase 00.