TL;DR: Ethereum developers have removed the planned October 26 Glamsterdam activation on Hoodi while they investigate EIP-8037 interactions with existing contracts; no replacement date has been announced.
Ethereum developers have pulled the October 26 activation of Glamsterdam on the Hoodi testnet, introducing a pause that matters directly to operators preparing for the next network upgrade.
The Ethereum Foundation said Thursday that developers want additional time to investigate how EIP-8037 interacts with existing mainnet smart contracts. The old Hoodi target, October 26 at 17:42:48 UTC, epoch 132,352, is no longer valid. A replacement activation time has not been chosen.
This is a testnet scheduling decision, not a rollback of transactions already confirmed on Hoodi, and it should not be presented as an announced delay to a specific Ethereum mainnet launch date.
The change extends beyond one activation flag
The decision removes the planned Amsterdam execution-layer activation and the Gloas consensus-layer activation from Hoodi’s schedule. It also drops the accompanying plan to raise the testnet gas limit to 200 million at that epoch.
Those details matter because network upgrades involve multiple pieces of client software agreeing on exactly when a change takes effect. If a validator or node follows the original schedule after everyone else has removed it, the result can be a chain incompatibility rather than a harmless configuration mismatch.
The Foundation has therefore told operators to check revised instructions for both execution and consensus clients. Earlier compatibility tables cannot be assumed to reflect the postponement. A client version that was correct for the previous schedule might now need a new configuration or update.
Why a testnet pause can be constructive
Major blockchain upgrades are supposed to encounter their difficult questions in testing, before real economic activity depends on the new rules. EIP-8037’s compatibility issue is the reason given for the pause, but the Foundation has not published a definitive diagnosis establishing a particular live exploit or failure.
The next useful signal will be a documented resolution, updated client releases and a fresh Hoodi activation epoch. Developers can then measure whether applications, block builders and validators behave as intended under the revised rules.
For ETH investors, the immediate effect is mainly on the upgrade calendar and development expectations. Ethereum’s existing mainnet continues to operate under its current rules. For infrastructure teams, however, the message is operational and urgent: do not leave an obsolete October 26 activation hard-coded in production-like test systems.
A cautious testnet postponement is less exciting than a launch, but it is precisely how an upgrade process should handle an unresolved compatibility concern.
Source: blog.ethereum.org original announcement or data.
Related Reading: Ethereum; smart contracts; staking.
Written by the News Desk and edited by Samuel Rae.