✓ Official source ETH
Ethereum postpones Glamsterdam on the Hoodi testnet, scrapping the Oct. 26 date with no new one set
⚪Neutral for $ETHIt is a testnet delay for further safety checks with no mainnet date ever set, so nothing changes for ETH holders yet.News sentiment, not financial advice. It reflects the likely impact of this news, not a price prediction.
Summary
The Ethereum Foundation said on Oct. 22 that the Glamsterdam network upgrade on the Hoodi testnet, previously set for Oct. 26, 2026 at 17:42:48 UTC (epoch 132,352), has been postponed and no new activation date has been set.
Core developers decided on All Core Devs call #248 to delay it so they can further investigate how EIP-8037 interacts with mainnet smart contracts, the foundation said; Glamsterdam went live on Sepolia on Oct. 6.
Glamsterdam combines the Amsterdam execution-layer and Gloas consensus-layer upgrades, headlined by enshrined proposer-builder separation (EIP-7732) and block-level access lists (EIP-7928); the delay also removes the planned raise of Hoodi's gas limit to 200 million.
Hoodi node and validator operators need client releases that drop the old activation, and the foundation said the delay does not set a mainnet date and requires no action from mainnet users or ETH holders.
Updates
- Update, : Oct. 22: The Ethereum Foundation said the Oct. 26 Glamsterdam activation on Hoodi has been postponed with no new date, after core developers on ACDE #248 decided to investigate further how EIP-8037 interacts with mainnet smart contracts. The delay also drops the planned 200M gas-limit increase; Hoodi node and validator operators should update to client releases that remove the old activation.
- Update, : Oct. 23: CoinDesk, Cointelegraph and Decrypt reported the reason behind the delay: security firm ChainSecurity found on Oct. 13 that two Glamsterdam gas changes, EIP-8037 and EIP-8038, could change how existing contracts handle failed calls, potentially letting failures be recorded permanently or making valid operations run out of gas. ChainSecurity said Friday it had found 13 real-world examples and is coordinating disclosure with affected projects, per Cointelegraph; CoinDesk said it has not shown a major production protocol is exploitable. Cointelegraph said developers had been considering early December for mainnet.
- Update, : Update (Oct. 27): CoinDesk reported developers merged a fix on Oct. 26 to Glamsterdam's deposit rules after a researcher found that a builder and validator sharing a public key could see both deposits credited to the builder. The researcher called these conditional findings, not confirmed live exploits, and no losses were reported; client teams still must implement the change, and Hoodi still needs a new date.
- Update, : Update (Nov. 6): The Ethereum Foundation said All Core Devs will not fork Hoodi for Glamsterdam until issues around EIP-8037 and EIP-8038 are resolved; Chainsecurity found projects that rely on gas-related invariants those EIPs would break. The EF posted a call for contract developers and auditors to check eight invariants that Glamsterdam would break and to contact [email protected] if affected, while work on Hegota continues in parallel. Cointelegraph reported the same delay and said the decision followed ChainSecurity's Oct. 13 findings on contracts that assume fixed gas costs when external calls fail.
Key facts
- Glamsterdam activates on Hoodi at epoch 132,352, slot 4,235,264 (Oct. 26, 2026, 17:42:48 UTC); it went live on Sepolia on Oct. 6.
- Hoodi’s gas limit will be raised to 200M at the activation epoch, matching Sepolia.
- The mainnet activation time will be announced once decided by client teams.
- Hoodi node operators and stakers must update both execution and consensus clients before activation.
- EIP-7773 tracks the upgrade and lists 18 scheduled EIPs, including ETH transfer logs (EIP-7708) and a SLOTNUM opcode (EIP-7843).
- Core developers decided on ACDE #248 to delay Glamsterdam on Hoodi to allow further investigation of EIP-8037's interactions with mainnet smart contracts.
- The postponement removes the scheduled Amsterdam and Gloas activations and the gas-limit raise to 200M; it does not revert Hoodi's chain history.
- Lodestar v1.50.1 and Besu 26.10.1 were the first client releases listed as incorporating the postponed Hoodi activation.
- ChainSecurity calculated that creating a new storage slot could require 110,020 gas when a separate allowance is exhausted, versus 22,100 under the old rules, CoinDesk reported.
- ChainSecurity said it has identified 13 real-world examples of contracts potentially affected and is coordinating responsible disclosure, without naming the projects, Cointelegraph reported.
- Cointelegraph said Ethereum developers had been considering early December for Glamsterdam on mainnet, pending successful Hoodi testing, and that the delay raises uncertainty over that timeline.
Related stories
- Indian exchange Unocoin keeps withdrawals frozen after spotting outgoing ether transfers from its BitGo wallets
- Binance sets aside $6.34 billion to cover record hack as TRM and Chainalysis tie it to North Korea's TraderTraitor
- Ethlabs shelves faster Ethereum blocks to push quantum-resistant accounts into 2027, two years ahead of the official roadmap