Skip to content

Preview & upcoming forks — Amsterdam

Status: Ready for the public MCP (not launched). Default lab fork — run under Amsterdam without naming an EIP.

This page is the home for preview execution-layer hardforks on the MCP: what you can run before mainnet catches up. When mainnet moves on, the current mainnet page is updated; the next scheduled fork gets a page here (e.g. Hegota after Amsterdam ships — same section, new row in the probe).

Amsterdam today

Amsterdam (alias Glamsterdam) is the upcoming EL fork and the default when you omit fork. You can run caller-supplied bytecode, a paid transaction, or a small lab block under Amsterdam rules.

You do not need to name an EIP. Omit fork or pass { "baseHardfork": "amsterdam", "eips": [] }. The probe lists summary, keywords, shapes, and advertised relatedEips.

Advertised runnable modules: 8024, 7843, 7708, 7928 (BAL via generate / inspect), 8037, 8038.

What you can ask your agent

  • “Run this bytecode under Amsterdam and tell me the gas used.”
  • “Simulate a 1 wei transfer to an empty account under Amsterdam.”
  • “What can I run under Amsterdam on this server — without picking an EIP?”
  • “Run the same program on Osaka then Amsterdam and diff gas and success.”

Workflow

StepAction
1Describe CapabilitiesnamedForks, eipIntroductions, Amsterdam relatedEips
2Run bytecode, Run transaction, or Run block — default Amsterdam; Osaka optional for mainnet-today compare

Fork caveat

The Amsterdam hardfork bundles the advertised modules. eips: [8024] is accepted but is not a before/after toggle on Amsterdam itself.

Preview vs mainnet today: run osaka then amsterdam (baselineForkId is Osaka until mainnet changes). For one EIP, use eipIntroductions: compare predecessor vs introducedAt (Amsterdam twins → usually Osaka vs Amsterdam).

Other bundled changes may execute in the client but stay uncatalogued until a shipped verb can show them honestly. Generic Amsterdam provenance keeps eips: [] and lists advertised modules in perEip.

Current mainnet (Osaka)Today’s EL baseline
Historical forksParis → Prague
CoverageLineage + EIP twins
EIP-7773Amsterdam / Glamsterdam meta

Changelog

Preview Forks (Amsterdam) Changelog
  1. v0.22026-09-16Framed as preview/upcoming section; room for post-Amsterdam forks (e.g. Hegota).
  2. v0.12026-09-16Named fork capability — generic Amsterdam runs.

Use = end-user reference. Internals = architecture and operations. Each section carries its own micro-changelog.