Coverage

Status: Catalogue for the upcoming public MCP (not launched). Runnable modules are those the hosted server will advertise via probe. Until then, use the website explorations.

Fork configuration is à la carte: a base hardfork plus an optional EIP list (runnable modules only — history is “run under Shanghai”, not “enable 3855 on Paris”). Named forks are catalog capabilities in the Berlin→Amsterdam lineage. A generic run under a named fork does not require naming an EIP.

Compare pattern: find the change in eipIntroductions → introducedAt → run the same verb on predecessorFork(introducedAt) and on introducedAt.

Lineage (live)

Order	Fork	Role	Aliases	Runnable twins	Doc bucket
0–5	berlin … prague	historical	see probe	7702 on prague	Historical forks
6	osaka	current	fusaka, mainnet-el	7883, 7951	Mainnet — Osaka
7	amsterdam	preview	glamsterdam	8024, 7843, 7708, 7928, 8037, 8038	Preview — Amsterdam

Full per-fork ids, aliases, and activatedEips live in describe_capabilities — the table above is the human map to three doc pages.

baselineForkId is osaka (current mainnet EL). Default lab fork is amsterdam.

Runnable capabilities (live catalog)

These appear in describe_capabilities() — engine modules with runnable: true. Comparison pairs on each row are derived from eipIntroductions (predecessor vs introducedAt).

EIP	Nature	Shapes	Introduced at	Compare (typical)	Catalogue
8024	new-capability	simulate	amsterdam	osaka → amsterdam	EIP-8024
7843	new-capability	block	amsterdam	osaka → amsterdam	EIP-7843
7702	new-exec-model	transaction, inspect	prague	cancun → prague	EIP-7702
7708	new-capability	transaction, simulate	amsterdam	osaka → amsterdam	EIP-7708
7883	repricing	simulate	osaka	prague → osaka	EIP-7883
7951	new-capability	simulate	osaka	prague → osaka	EIP-7951
8037	new-exec-model	transaction, simulate	amsterdam	osaka → amsterdam	EIP-8037
8038	repricing	simulate, transaction	amsterdam	osaka → amsterdam	EIP-8038

Amsterdam note (8024 / 7843): The Amsterdam hardfork already bundles these EIPs. Passing eips: [8024] or eips: [7843] is accepted but is not a pre/post toggle.

Exploration twins (human catalogue)

Every live website exploration has an MCP-docs page mapping the same problem set. Status may be Runnable or Planned.

EIP	Exploration twin	MCP status	Page
8024	Stack opcodes	Runnable	EIP-8024
7883	ModExp gas	Runnable	EIP-7883
7951	secp256r1	Runnable	EIP-7951
7928	Block access lists	Runnable (generate, inspect)	EIP-7928
7843	SLOTNUM opcode	Runnable	EIP-7843
7702	Set-code EOA	Runnable	EIP-7702
7708	ETH transfer logs	Runnable	EIP-7708
8037	State creation gas	Runnable	EIP-8037
8038	State-access gas	Runnable	EIP-8038

PeerDAS (7594) has no MCP twin — listed in eipIntroductions at Osaka with no observable shape in this lab.

Canonical metadata for twins lives in website src/explorations/eip-NNNN/canonical.ts.

Changelog

Coverage Changelog

1. v0.232026-09-16Lineage extended with Berlin and London (historical floor); glacier BPO forks excluded.
2. v0.222026-09-16Fork docs: preview (Amsterdam), mainnet (Osaka), combined historical page.
3. v0.212026-09-16Paris→Amsterdam lineage table; eipIntroductions compare pattern; Prague no longer ModExp-only.
4. v0.202026-09-16Named forks are catalog capabilities — generic Amsterdam / Osaka / Prague runs; advertised relatedEips; fork catalogue pages.
5. v0.182026-09-14EIP-8038 named catalog row — SSTORE via run_transaction; SLOAD/EXTCODESIZE via run_bytecode.
6. v0.172026-09-11EIP-8038 exploration twin — simulate gasUsed shows the SSTORE write jump; named catalog row follows.
7. v0.162026-09-10EIP-7843 SLOTNUM runnable — run_block header.slotNumber; catalog row live.
8. v0.152026-09-10run_block lab verb shipped — header.slotNumber; 7843 catalog still Planned.
9. v0.142026-09-10EIP-7843 exploration twin — Planned until run_block / header slot on simulate.
10. v0.132026-09-087708/8037 shapes include transaction (run_transaction); simulate remains for bytecode/precompiles.
11. v0.122026-09-08EIP-8037 named catalog row — simulate gasUsed (Amsterdam vs Osaka first-touch and new-slot).
12. v0.112026-09-07EIP-8037 exploration twin — simulate gasUsed already shows first-touch state gas; named catalog row follows with the engine module.
13. v0.102026-09-02Catalogue is for the hosted MCP — removed self-host / local early-access framing.
14. v0.92026-08-31Split runnable catalog vs exploration twins; note public MCP not launched.
15. v0.82026-08-27Osaka mainnet baseline fork — run-twice comparisons against Amsterdam preview.
16. v0.72026-08-27EIP catalogue pages under use/eips/ — 8024 human entrypoint.
17. v0.62026-08-278024 module is opcode/encoding support, not demo replay.
18. v0.52026-08-27Slim catalog to runnable EIP-8024 only — questions, scenarios, no stub EIPs.
19. v0.32026-07-20Split from execution-engine — user-facing EIP coverage under use/.