Ethereum core developers have officially decided to delay the implementation of the highly anticipated Glamsterdam upgrade on the Hoodi testnet. The postponement comes as the development community works to investigate and address pressing security concerns tied to eight smart contract invariants highlighted in recent audit reports concerning Ethereum Improvement Proposals (EIP) 8037 and 8038.
The decision to hit the pause button on the Hoodi network fork was announced by the Ethereum Foundation in a blog post, underscoring the ecosystem’s cautious approach to mainnet deployments and protocol-level modifications. According to the Foundation, the delay will afford developers critical time to thoroughly analyze potential vulnerabilities, assess the broader impact on existing applications, and determine whether foundational changes are required before Glamsterdam continues on its trajectory toward the mainnet.
The root of the current caution traces back to an October 13 security report published by smart contract auditor ChainSecurity. The security firm identified that EIP-8037 and EIP-8038—two core components of the forthcoming Glamsterdam upgrade—alter how gas is priced and charged for specific execution operations. Crucially, the auditors discovered that these pricing alterations could inadvertently break existing smart contracts across the Ethereum ecosystem.
Many established Ethereum decentralized applications and protocols have operated under long-standing assumptions that specific underlying operations carry a fixed, predictable cost in gas. When these economic and execution assumptions are suddenly disrupted, particularly in scenarios where external calls fail, the resulting behavior can invalidate the security invariants that protect the smart contracts. This mismatch between legacy contract code and the new gas-charging mechanics poses risks that developers are eager to mitigate well before the upgrade touches production environments.
The Ethereum Foundation emphasized that the Hoodi testnet fork will remain on hold until these specific smart contract issues are fully understood, addressed, and resolved. By prioritizing thorough testing and peer review during this pre-deployment phase, core developers aim to safeguard the network and its vast ecosystem of decentralized finance applications, token protocols, and smart contract systems against unexpected operational failures upon rollout.
This cautious recalibration follows active testing phases elsewhere on the network. Ethereum’s Glamsterdam upgrade previously went live on the Sepolia testnet on October 6, marking one of the final major rehearsals in the lead-up to the mainnet release. Sepolia’s successful progression offered developers valuable telemetry data regarding the upgrade’s performance under near-mainnet conditions.
The overarching Glamsterdam upgrade represents a substantial leap forward in Ethereum’s long-term layer-1 scaling roadmap. As detailed in a previous roadmap announcement from the Ethereum Foundation, the upgrade is designed to introduce several foundational architectural shifts. These include enshrined proposer-builder separation, which aims to structurally address validator centralization and MEV extraction risks; block-level access lists, which optimize execution efficiency and state access; and nuanced adjustments to gas pricing intended to more accurately reflect the true computational and storage costs of transaction execution on the network.
While these protocol enhancements are widely regarded as vital for Ethereum’s scalability and economic efficiency, the ChainSecurity findings illustrate the delicate balance required when modifying core execution parameters on a multi-billion-dollar decentralized network. By halting the Hoodi testnet deployment, the Ethereum developer community is signaling its commitment to robust security practices, ensuring that network upgrades do not introduce systemic risks to the millions of smart contracts currently securing user assets across the globe.
