Glamsterdam Countdown
Live countdown to Glamsterdam, the Ethereum hard fork after Fusaka, with activation epochs per network and a client-by-client readiness matrix that fills in as fork-ready releases land.
No activation epoch announced yet
Glamsterdam is in its final multi-client devnets (glamsterdam-devnet-5 and -6); public testnets fork next, with mainnet loosely targeted for the second half of 2026. The countdown starts here the moment the first activation epoch is announced.
Client readiness matrix
No client has published a stable Glamsterdam-ready release yet. The tables below fill in as client teams cut releases and the Ethereum Foundation's fork announcement declares the official minimum versions.
Execution clients
| Client | Fork-ready version | Releases |
|---|---|---|
| Geth | none yet | GitHub |
| Nethermind | none yet | GitHub |
| Besu | none yet | GitHub |
| Erigon | none yet | GitHub |
| Reth | none yet | GitHub |
Consensus clients
| Client | Fork-ready version | Releases |
|---|---|---|
| Lighthouse | none yet | GitHub |
| Prysm | none yet | GitHub |
| Teku | none yet | GitHub |
| Nimbus | none yet | GitHub |
| Lodestar | none yet | GitHub |
| Grandine | none yet | GitHub |
What ships in Glamsterdam
EIP-7732: Enshrined proposer-builder separation (ePBS). Splits the slot into a consensus phase and a later execution phase, moving the proposer/builder handshake into the protocol and removing the mev-boost relay trust assumption.
EIP-7928: Block-level access lists (BALs). Blocks declare up front which state they touch, so clients can execute transactions in parallel and validate blocks much faster.
The final EIP list is tracked in meta EIP-7773. We covered both headliners in depth on the blog: what ePBS means for searchers and builders and block-level access lists explained.
How fork activation works
Hard forks activate at a beacon-chain epoch, not a calendar date. An epoch is 32 slots of 12 seconds, so once the epoch is announced the wall-clock time is fixed: genesis time plus epoch times 384 seconds. That is exactly what the countdown above computes. Client teams then ship releases with the fork configured, and every node operator has to be on a ready version of both clients before the epoch arrives.
If you would rather not babysit fork upgrades, BLAZED.sh nodes are upgraded for you well ahead of every activation epoch, on testnets and mainnet alike.
Frequently asked questions
When is the Glamsterdam hard fork?
No mainnet activation epoch has been announced yet. Glamsterdam is in its final multi-client devnets (glamsterdam-devnet-5 and -6); public testnets fork next, with mainnet loosely targeted for the second half of 2026. This page updates as soon as epochs are set.
What is the Glamsterdam upgrade?
Glamsterdam is the Ethereum hard fork that follows Fusaka. Its two headline changes are enshrined proposer-builder separation (EIP-7732) and block-level access lists (EIP-7928); the full scope is tracked in meta EIP-7773.
Which client versions are Glamsterdam-ready?
No stable Glamsterdam-ready client releases exist yet. Once client teams cut them, the matrix on this page lists the minimum version per client, with the Ethereum Foundation's fork announcement as the authoritative source.
What happens if I don't upgrade my node before the fork?
An un-upgraded node keeps applying pre-fork rules, so at the activation epoch it splits onto a chain the rest of the network considers invalid. It stops finalizing, serves stale data, and any validators behind it leak until they are upgraded. Both the execution and the consensus client have to be updated.
Do testnets fork before mainnet?
Yes. Glamsterdam activates on public testnets such as Sepolia, Holesky and Hoodi first, typically a few weeks apart, and the mainnet epoch is only scheduled once the testnet forks have run cleanly.
Building on Ethereum?
Run your code on the node itself. No rate limits, no compute units, flat rate, sub-10ms RPC.