Glamsterdam’s Hoodi date just got pulled — gas security first

Testnet calendars are supposed to be boring. This one just became a plot twist.

Ethereum’s Glamsterdam upgrade — already live on Sepolia since October 6 — was scheduled to hit the Hoodi testnet on October 26 (epoch 132,352, with a planned gas-limit bump to 200M). That activation is postponed. No replacement date yet. The earlier Hoodi countdown notes are superseded until client teams and researchers finish the homework that triggered the pause.

Why yank a date that was already on every operator checklist?

Because Glamsterdam isn’t a cosmetic fork. Beside enshrined proposer-builder separation and block-level access lists, it rewires gas and state-cost accounting so creating and touching state reflects real load. Security reviewers flagged that some of those gas-rule changes can interact badly with existing contracts — specifically patterns meant to defend against insufficient-gas griefing, where a call is starved just enough to fail in ways the author didn’t budget for. When your “safe” assumptions about remaining gas stop matching the protocol’s new meter, old defenses can get weird. Pausing Hoodi is the grown-up response: find out how weird before you invite the whole validator set to a dress rehearsal.

What this is not: a mainnet emergency. Mainnet was never given a public activation slot for Glamsterdam. Sepolia already carried the earlier test. Hoodi was the next stress environment — including that 200M gas-limit experiment — and it’s now on hold until the gas/security questions have clearer answers and client releases catch up.

For early-stage watchers, the signal is process, not panic.

L1 scaling roadmaps live or die on whether boring safety work can interrupt a marketing calendar. Pulling Hoodi says the interrupt still works. The cost is uncertainty: December-ish mainnet chatter gets fuzzier until Hoodi actually sticks the landing. App teams that already started gas-estimation drills against Glamsterdam rules should keep testing — and treat any “fixed stipend” contracts as guilty until proven innocent under the new schedule.

Node operators on Hoodi: don’t chase the old October 26 cutover. Wait for the revised activation note and matching client tags. Everyone else can keep building. Just don’t screenshot a dead epoch number into your roadmap deck and call it a plan.