Seventeen walkthroughs is a lot to land on. These are three reading orders through the ones that already exist — one per audience. No new material, just the order that makes them make sense and the reason each step follows the last.
Three functions, then the one surprise worth knowing before you build anything. Here to ship, not read? Deploy a contract on the EEZ testnet — about fifteen minutes, no walkthroughs required.
Learn how the answer is written down before your transaction runs, instead of being fetched while you wait.
Learn how the value that comes back decides what the rest of your transaction does — and why that removes the callback, the timeout and the retry you would otherwise have to write.
Learn why every onlyOwner, allowlist and approve on the far side keys to a proxy address instead of your contract — and why nothing reverts when it does.
Then, when you hit them: is this address a proxy, why you can't call the manager directly, your contract's address on another rollup, encoding a call's content hash.
The same three steps as runnable tests, on your own machine. No testnet, no Docker — the snippets carry no forge-std and no submodules, so they build on a bare checkout. You need Foundry v1.7.1 and nothing else.
git clone https://github.com/0xarmagan/eez-demos.git cd eez-demos/starter && ./run.sh # or run one step at a time, from eez-demos/snippets: forge test --match-test test_routedReadReturnsThePreCommittedEntry -vv # 01 forge test --match-test test_theBranchTracksTheValueNotTheSuccessFlag -vv # 02 forge test --match-test test_sameChainCheck_revertsWhenCalledViaProxy -vv # 03 # expected: ./run.sh prints one line per step, all three ending # pass # anything else prints the failing test's output below the step.
Already a sequence — it just was never labelled as one. Each step assumes the one before it.
Learn how to bring up the node, proof-signer and the L1 in a disposable network.
Learn what lands on L1 and L2, and in what order, once the network is up.
Learn what changes when the L1 underneath you is Chiado rather than a disposable devnet.
Learn how to drive traffic through the stack you just brought up, and how to tell that it worked.
What the system is, then the two decisions that shape everything else about it.
Learn how sequencer, composer, proof-signer and deriver each fit.
Learn why the L2 block is added immediately and rolled back if L1 never confirms it.
Learn what is actually checked before a batch is accepted, and by whom.
Reference, when you need them: the deriver, how the address is derived, the rolling hash.