Hoodi's October 26 Glamsterdam activation is postponed: check both clients

News3 min read

Hoodi's October 26 Glamsterdam activation is no longer scheduled. Read the revised execution and consensus client instructions; mainnet users need no action.

Fictional Hoodi testnet comic: Brokzi removes a cancelled October26 activation card from a forward-planning board and checks execution and consensus client settings. The existing chain remains intact; no new date or mainnet change is depicted.
AI-assisted editorial illustration · Brokzi
On this page

What happened

The Ethereum Foundation Protocol Cluster's October 22 announcement postpones Glamsterdam on Hoodi. It cites further investigation of EIP-8037 interactions with mainnet smart contracts. That stated investigation is not a report that an exploit has occurred.

The announcement supersedes the activation instructions covered in our original Hoodi timetable report. We checked the current notice and linked Geth and Lighthouse releases on October 24. This is follow-up reporting on the October 22 decision, not a new postponement announced today.

What is confirmed

The old activation coordinates were October 26, 2026, 17:42:48 UTC, epoch 132352. The Foundation says that future schedule, including the associated 200 million gas setting, has been removed. There is no replacement date in the notice.

Removing future configuration does not reverse Hoodi's chain history. It also does not activate these changes on mainnet. A cancelled testnet calendar entry and a chain rollback would be different events.

CheckExecution layerConsensus layer
Previously scheduled componentAmsterdamGloas
Required readingYour execution client's revised Hoodi release notesYour consensus client's revised Hoodi release notes
Validator setupExecution-client instructions still applyCheck both beacon-node and validator-client instructions

Why it matters for Hoodi operators

Two independently published releases make the practical problem concrete. Geth v1.17.10 cancels Amsterdam on Hoodi. Its notes tell Hoodi operators on v1.17.9 to upgrade before the former activation time and say other networks are unaffected. That is Geth-specific guidance, not a version recommendation for every execution client.

Lighthouse v8.3.2 disables Hoodi's scheduled Gloas fork and supersedes the Hoodi instructions in v8.3.0 and v8.3.1. Its staking-user instructions cover the beacon node, validator client and execution client. For upgrades from v8.2.x or earlier, it also points readers to prior migration and system requirements. Mainnet users do not need that release because of this Hoodi change.

The Foundation's current client table has more entries than the earlier snapshot. We are not reproducing it as a permanent installation checklist: it includes a release-candidate entry, and notes may change. Follow the live Foundation links and the instructions for the clients you actually run. Builder infrastructure has its own provider instructions too.

What remains unknown

A replacement Hoodi activation and a Glamsterdam mainnet date remain unannounced in this notice. The reason for investigating a proposed change does not establish which final implementation or timetable developers will choose.

Brokzi has not installed these releases, inspected a reader's node or independently measured network readiness. This report identifies the changed instructions; it does not certify any operator's configuration. Nor does a testnet gas-limit change establish a mainnet fee outcome: gas limit and gas price are separate measurements.

Brokzi's Take

Check the instruction behind the date before relying on a saved upgrade reminder. For a Hoodi setup, identify both clients and confirm their notes expressly remove the former activation. Check validator and builder components where applicable; an old download list is not proof of an updated setup.

For a mainnet wallet holder, this announcement supplies no migration, claim or token-transfer task. Keep testnet operations separate from the assets in your wallet. Our Ethereum explainer covers those different network roles.

Sources

Primary sources checked October 24, 2026. Event date is the Foundation's October 22 announcement; no publication hour is supplied. Client releases are attributed examples, not an exhaustive compatibility table or a performed software upgrade. The illustration is fictional, not a screenshot or evidence of an activated fork.

See something wrong? Brokzi logs material changes. Prepare a correction note.

About the byline

Brokzi Editorial

The accountable byline for Brokzi’s explainers, definitions, news notes, and corrections.

Editorial responsibility →