Skip to content

Preview & upcoming forks — Glamsterdam

Status: Ready for the public MCP (not launched). Default lab fork — run under Glamsterdam 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 Glamsterdam ships — same section, new row in the probe).

Glamsterdam today

Glamsterdam (EL alias amsterdam) 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 Glamsterdam rules.

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

Advertised runnable twins:

EIPPage
8024DUPN / SWAPN / EXCHANGE
7843SLOTNUM
7708ETH transfer logs
7928BAL (generate / inspect)
8037State creation gas
8038State-access gas

What you can ask your agent

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

Workflow

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

Fork caveat

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

Preview vs mainnet today: run fusaka then glamsterdam (baselineForkId is Fusaka until mainnet changes). For one EIP, use eipIntroductions: compare predecessor vs introducedAt (Glamsterdam twins → usually Fusaka vs Glamsterdam).

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

Current mainnet (Fusaka)Today’s EL baseline
Historical forksParis → Pectra
EIP catalogueLineage + EIP twins
EIP-7773Glamsterdam meta

Changelog

Preview Forks (Glamsterdam) Changelog
  1. v0.42026-09-17Twin pages linked from this fork doc (sidebar no longer lists EIPs).
  2. v0.32026-09-17Canonical catalog id is glamsterdam; amsterdam is the EL alias.
  3. v0.22026-09-16Framed as preview/upcoming section; room for post-Glamsterdam forks (e.g. Hegota).
  4. v0.12026-09-16Named fork capability — generic Glamsterdam runs.

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