HomeCrypto NewsWeb 3Ethereum's Glamsterdam Goes Live on Sepolia; Hoodi Date Postponed

Ethereum’s Glamsterdam Goes Live on Sepolia; Hoodi Date Postponed

Network upgrades on Ethereum do not flip a single switch worldwide. They activate at a scheduled slot after node operators have opted in by updating software. The next one on a public testnet, Glamsterdam, went live on the Sepolia testnet on 6 October 2026.

According to the Ethereum Foundation Protocol blog, Glamsterdam was scheduled to activate on Sepolia at epoch 353,024, slot 11,296,768 — 6 October 2026, 13:53:36 UTC (14:53 London). [1] Ethereum community contributor Pooja Ranjan said it went live at that time, and CoinTelegraph reported the upgrade as live on Sepolia the same day. [2] A Hoodi date of 26 October was set and has since been postponed with no new date (see updates below); the mainnet date is still undecided. This coverage is about Sepolia only.

A “testnet” is a practice network that mirrors mainnet rules without using real mainnet funds. A “hard fork” here means a coordinated protocol upgrade that nodes must support to stay on the upgraded chain.

Update, 22 October 2026: Glamsterdam on Hoodi is postponed, with no new date

The Hoodi activation set for 26 October is off. “The Glamsterdam upgrade on Hoodi, previously scheduled for October 26, 2026 at 17:42:48 UTC (epoch 132,352), has been postponed. A new activation date has not been set,” the Ethereum Foundation said in a blog post on 22 October.

Core developers decided on the ACDE #248 call to delay the upgrade “to allow for further investigation of interactions of EIP-8037 with mainnet smart contracts”, the Foundation said. EIP-8037 is one of the gas-repricing changes for state creation described below. The delay “also removes the gas-limit schedule that would have raised Hoodi’s gas limit to 200M at the same epoch”. The Foundation added: “This rolls back the configuration for a future upgrade; it does not revert Hoodi’s chain history.”

Hoodi node and validator operators are told to check both execution and consensus clients for releases that reflect the postponement before 26 October. Software still scheduling Glamsterdam at the old time “need[s] to be updated to match the revised Hoodi configuration”. The Foundation says the release tables in its earlier announcement are not confirmation that those versions include the postponement.

For everyone else: “It does not set a Glamsterdam mainnet activation date, and no action is required from Ethereum mainnet users or ETH holders as a result of this update.”

Update, 16 October 2026: Glamsterdam is scheduled for the Hoodi testnet on 26 October

This schedule was postponed on 22 October; see the update above. The Ethereum Foundation has set a date for Glamsterdam’s next testnet. In a blog post on 16 October, it said the upgrade “is scheduled to activate on Hoodi at epoch 132,352, slot 4,235,264 (October 26, 2026, 17:42:48 UTC)”, which is 18:42:48 London time. “At the same epoch, Hoodi’s gas limit will be raised to 200M,” the Foundation added.

Hoodi is the second testnet after Sepolia, where Glamsterdam went live on 6 October. “The mainnet activation date has not yet been decided,” the Foundation said.

Node operators running Hoodi “must update both their execution and consensus layer clients before activation”. The Foundation says compatible client versions will be added to its release tables as they are confirmed. The headline changes are the same as on Sepolia: enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928) and gas repricing for state creation and access (EIP-8037 and EIP-8038).

What Glamsterdam changed on Sepolia

Glamsterdam combines the Amsterdam execution-layer upgrade with the Gloas consensus-layer upgrade. Its headlining changes are EIP-7732 (enshrined proposer-builder separation, or ePBS) and EIP-7928 (block-level access lists, or BALs), plus gas and state-pricing updates. [1]

In plain terms, ePBS builds the split between who proposes a block and who builds its execution payload into the consensus protocol itself, reducing reliance on trusted middleware for that exchange. BALs record which accounts and storage slots a block touches, so clients can read state and validate work more efficiently in parallel. [1]

Gas accounting also shifts. EIP-8037 and EIP-8038, among others, reprice state creation and state access. The Foundation warns that contracts which hardcode gas stipends or assume leftover gas may need testing and updates. [1]

Trade press also notes an opt-in push toward much larger blocks on Sepolia for the rehearsal, including a last-minute Prysm client fix so some validators would propose at a higher gas target rather than the previous default. That capacity test is specific to Sepolia and is not a mainnet gas limit. [3]

Sepolia node operators had to update two clients

Sepolia node operators and stakers (the role explained in our staking guide) had to update both execution and consensus clients to releases that explicitly supported the scheduled Sepolia activation. The Foundation published Sepolia-compatible release tables in its announcement. [1]

Ordinary Ethereum mainnet users and ETH holders need do nothing for this Sepolia event. Mainnet will get a separate schedule when client teams decide dates; the same applies to holders using broker products such as Interactive Brokers’ Ethereum staking, which run on mainnet. [1][2]

ePBS and access lists change how Ethereum blocks are built

ePBS and BALs are foundational layer-1 scaling changes. They affect how blocks are built and validated and how clients parallelise state access—material for Ethereum engineering teams and for apps whose gas assumptions may change after the fork. Sepolia is one of the last major public rehearsals before teams set Hoodi and, later, mainnet dates. [2]

Open questions before Hoodi and mainnet

  • How the Sepolia rehearsal will score over the coming days on validator agreement, block propagation and app compatibility; early “live” reports are not a full post-mortem. [2][3]
  • When Hoodi and mainnet will activate. The Hoodi activation set for 26 October has been postponed with no new date, and the Foundation says the postponement does not set a mainnet date (see 22 October update).
  • How widely application gas estimates will break after repricing; outcomes will vary by contract. [1]

The Hoodi delay shows Glamsterdam’s testnets doing their job

Glamsterdam activated on Sepolia on 6 October 2026 as a scheduled testnet hard fork centred on ePBS, block-level access lists and gas repricing. That was a rehearsal, not a mainnet go-live, and the weeks since have shown why the rehearsals exist. Developers paused the Hoodi step to study how EIP-8037’s repricing of state creation interacts with contracts already on mainnet, and used the extra time to merge a fix for a fork-time bug that could have diverted staking deposits.

Both problems are the kind that only surface when real client software runs a fork end to end, and both were caught before any real ETH was at stake. The cost is time: with Hoodi unscheduled, the Foundation has not set a mainnet date, and a gas-repricing question tied to existing contracts may take longer to settle than a client bug. For application teams, the practical message is unchanged. Contracts that hardcode gas stipends or rely on leftover gas should be tested against the new pricing now, rather than after a mainnet date is announced.

Sources

  1. Ethereum Foundation Protocol blog, Glamsterdam Testnet Announcement, 17 September 2026 — https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement
  2. CoinTelegraph, Zoltan Vardai, 6 October 2026: report that Glamsterdam went live on Sepolia — https://cointelegraph.com/news/ethereums-glamsterdam-upgrade-launches-on-sepolia-testnet
  3. CoinDesk, 6 October 2026: report on the Prysm update and Sepolia capacity test ahead of activation — https://www.coindesk.com/tech/2026/10/06/ethereum-s-glamsterdam-test-gets-last-minute-fix-before-major-capacity-jump
  4. Ethereum Foundation: Glamsterdam Hoodi announcement https://blog.ethereum.org/en/2026/10/16/glamsterdam-hoodi-announcement
  5. Ethereum Foundation Protocol Cluster, Glamsterdam on Hoodi Postponed, 22 October 2026 — https://blog.ethereum.org/en/2026/10/22/glamsterdam-hoodi-delay
  6. Ethereum Improvement Proposals: EIP-7732, Enshrined Proposer-Builder Separation — https://eips.ethereum.org/EIPS/eip-7732

Related stories

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.