Ethereum Client Teams Unschedule Hoodi Testnet Glamsterdam Upgrade

Ethereum client developers have unscheduled the Glamsterdam network upgrade previously planned for the Hoodi testnet, pulling activation parameters across multiple execution and consensus repositories on Oct. 22 ¹². The decision follows an agreement reached during the All Core Developers Execution (ACDE) call #248, calling off the deployment set for epoch 132352 on Oct. 26 ². At the time of writing, $ETH traded at $2,382, down 3.8% over the past 24 hours.

The coordinated rollback was initiated upstream in the eth-clients/hoodi repository via pull request #33, which stripped amsterdamTime from the testnet's genesis file and reverted the GLOAS_FORK_EPOCH setting to a far-future value ². Client teams moved immediately to integrate the change to prevent nodes from diverging or splitting off from the testnet ². Hyperledger Besu developers opened pull request #11709 to unschedule the upgrade, reverting the previous scheduling commit while recording the adjustment under unreleased changes ¹. Simultaneously, client teams for Lodestar, ethlambda, and ethrex updated their respective Hoodi configurations ².

Client Configurations Reverted

Beyond reverting the fork epoch, the update removes the experimental GAS_LIMIT_SCHEDULE entry that was scheduled to lift Hoodi's gas limit to 200 million gas at epoch 132352 ². As reported when Ethereum developers canceled the Oct. 26 Glamsterdam upgrade on Hoodi testnet, core teams opted against activating the upgrade without further readiness testing. Presets and version flags for the upgrade remain preserved in client codebases so developers can reschedule activation by modifying a single epoch value once a revised timeline is finalized ². Node operators on Hoodi must update their client configurations to match the upstream repository to remain aligned with the canonical testnet chain ².