Skip to content

Analysis · Protocol

How an Ethereum upgrade actually ships: the Glamsterdam testnet delay as a case study

On 22 October 2026 core developers postponed Glamsterdam's activation on the Hoodi testnet to investigate one gas-repricing EIP. The episode shows the real path from proposal to mainnet, and why firm dates deserve scepticism.

By Etherelysium Editorial TeamUpdated 18 November 20263 min read

How an Ethereum upgrade actually ships: the Glamsterdam testnet delay as a case study
Share X LinkedIn

Coverage of Ethereum upgrades tends to report dates and price implications. The process underneath is public, documented and slower than the headlines, and the most recent example is a useful map of how it works.

What happened

Glamsterdam is the upgrade after Fusaka, which activated on mainnet on 3 December 2025. On 17 September 2026 Ethereum’s protocol blog (blog.ethereum.org) published a testnet announcement scheduling Glamsterdam on the Sepolia testnet for 6 October 2026, and stating that “Hoodi and mainnet activation dates have not yet been decided”. A Hoodi activation was later set for 26 October 2026. On 22 October 2026 a follow-up post announced that developers had decided on the execution-layer core developers call (ACDE #248) to postpone it, “to allow for further investigation of interactions of EIP-8037 with mainnet smart contracts”. No new date was set. The post also said it “does not set a Glamsterdam mainnet activation date” and that no action was required from mainnet users or ETH holders.

As of 18 November 2026, ethereum.org’s roadmap page lists Glamsterdam as in development with a target of Q4 2026, and the next upgrade, Hegotá, for 2027 with scope not final. A target on a roadmap is not a scheduled activation.

What is in it

The September announcement lists the headline changes: EIP-7732, enshrined proposer-builder separation, in which a proposer commits to a builder’s payload that the builder reveals afterwards; EIP-7928, block-level access lists that record which accounts and storage slots a block touches so clients can process it more efficiently; and a set of gas repricings, including EIP-8037, which raises the gas cost of creating new state. It is the repricing, not the headline features, that triggered the delay: changing what operations cost can break contracts that assumed the old prices.

The path every change follows

A change starts as an Ethereum Improvement Proposal. EIP-1 defines the status field that tells you how far along it is: Draft is “the first formally tracked stage”, Review and Last Call are peer review, Final is “the final standard”. Core protocol EIPs also need client implementations, and inclusion in a named upgrade is coordinated on the public All Core Developers calls. Then comes a sequence of testnets, client releases with the fork configuration, and finally a mainnet epoch. Node operators have to update their software; the Fusaka mainnet announcement notes that upgrades “require explicit opt-in from node operators”. Anyone holding ETH in a wallet does nothing.

The Settlement Test, applied to an upgrade

  • What settles: new rules take effect at a specified epoch, for every node running updated software, at the same moment. Before that, nothing has changed on mainnet.
  • What it costs: for node operators, an update and some testing. For contracts, repricings can change what existing code costs to run, which is exactly what developers paused to check.
  • What breaks: nodes that do not update follow the old rules and fall off the canonical chain; a repricing that breaks deployed contracts would land on every user of them, which is why a testnet date moved.

How to follow upgrades without the noise

Read the EIP and its status. Read the protocol blog’s announcements, which give epochs and client versions. Read client release notes for what actually shipped. Treat any firm mainnet date without a linked announcement as unconfirmed, and any article that describes an upgrade only by its expected price effect as not about the upgrade. For what the last two upgrades changed, see rollup fees run on two meters and smart accounts after Pectra, and for the fork-choice background, our guide to finality and reorgs.

Primary sources

Educational content, human-edited and possibly AI-assisted. It describes how systems work and is not financial, legal or tax advice. Report an error via our corrections page.

More in Protocol

Related articles

See all