- Ethereum canceled Hoodi’s October 26 activation without setting a replacement date.
- Developers are examining whether gas changes could disrupt existing contract safeguards.
- Hoodi operators must review client updates; mainnet users need no action.
Ethereum developers have postponed Glamsterdam on the Hoodi testnet while investigating how proposed gas changes affect existing smart contracts. The Ethereum Foundation announced the decision on October 22, canceling the activation scheduled for October 26. No replacement date has been set, and the notice does not require action from mainnet users or ETH holders.
Glamsterdam delay removes Hoodi activation and gas increase
Developers agreed to the postponement during All Core Developers Execution call 248. Their investigation focuses on EIP-8037, which changes charges for creating blockchain state and introduces separate gas accounting.
The canceled activation was scheduled for 17:42:48 UTC at Hoodi epoch 132,352. Updated settings remove both Amsterdam, the execution-layer component, and Gloas, its consensus-layer counterpart.
The Glamsterdam delay also removes the planned increase in Hoodi’s gas limit to 200 million. These configuration changes affect a future upgrade and leave the testnet’s existing transaction history intact.
The Foundation has not confirmed a mainnet activation date. Previously discussed December dates therefore remain proposals rather than an approved deployment schedule.
Glamsterdam gas changes raise concerns over failed calls
ChainSecurity’s October 13 assessment explains how revised gas accounting could disrupt safeguards in deployed contracts. Its analysis covers EIP-8037 alongside EIP-8038, which changes the cost of accessing existing state.
Some contracts inspect remaining gas after an external call fails to decide whether the transaction should revert. Reverting can preserve the opportunity to retry an operation that received too little gas.
Under Glamsterdam, gas refills and changed charges could let failure handlers finish when they previously could not. An application might consequently record a permanent failure even though the original operation should remain retryable.
The concern involves changed execution behavior without any modification to the affected contract’s code. Developers therefore need to examine failure handling, rather than assume that unchanged applications will behave identically after the upgrade.
Hoodi operators must check execution and consensus clients before October 26, including validator and external builder software. Release notes should explicitly confirm removal of the canceled activation.
The Foundation currently lists Lodestar v1.50.1, Besu 26.10.1 and Nethermind 2.2.1 among updated releases. Ethrex v30.0.1-rc.2 is listed as a prerelease.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. CoinCryptoNewz is not responsible for any losses incurred. Readers should do their own research before making financial decisions.
