Ethereum developers delay Glamsterdam hardfork following discovery of critical gas-related smart contract vulnerabilities

The Ethereum development community has officially elected to pause the progress of the highly anticipated Glamsterdam hardfork, following the discovery of significant vulnerabilities that could compromise existing decentralized applications. The decision comes after extensive testing on various Ethereum testnets revealed that the implementation of EIP-8037 and EIP-8038—two core components of the update—would fundamentally alter the gas pricing mechanisms for specific operations and state storage. These modifications threaten to break critical invariants upon which numerous live, immutable smart contracts rely, potentially leading to widespread operational failures across the Ethereum ecosystem.
The Technical Catalyst: EIP-8037 and EIP-8038
At the heart of the current postponement are two Ethereum Improvement Proposals (EIPs) designed to optimize the efficiency of the Ethereum Virtual Machine (EVM). EIP-8037 and EIP-8038 aim to restructure the gas cost architecture for state access and specific opcode executions. While these changes are intended to improve the network’s long-term sustainability and reduce technical debt, they inadvertently shift the economic and operational thresholds that many legacy contracts utilize to ensure their own security and functionality.
When a smart contract is deployed, it often operates under the assumption that certain gas costs will remain constant. Many sophisticated protocols, such as decentralized exchanges, lending platforms, and cross-chain bridges, utilize "gas-aware" logic to prevent reentrancy attacks or to manage state transitions. By changing the underlying cost structure, these updates render the original assumptions of these contracts invalid. The security firm Chainsecurity, which conducted the initial analysis, identified that these changes would break core invariants, effectively creating "logic traps" where previously secure code could become vulnerable to exploitation or become permanently bricked.
Chronology of the Postponement
The realization of these vulnerabilities triggered an immediate shift in the development timeline. The AllCoreDev (ACD) group, responsible for coordinating Ethereum’s roadmap, moved quickly to stall the deployment of the Hoodi upgrade, which was intended to follow the initial testing phase.
- Early November 2026: Initial reports from Chainsecurity surfaced regarding the potential for broken invariants during Glamsterdam testnet runs.
- November 6-7, 2026: ACD developers convened to evaluate the findings, resulting in the decision to halt progress on Hoodi until a comprehensive audit of the impact on live contracts could be completed.
- November 9, 2026: The Ethereum Foundation published an official update acknowledging the receipt of four credible reports of affected deployed contracts.
- November 12-19, 2026: A critical window for communication, including the AllCoreDev Consensus (ACDC) meeting and the upcoming AllCoreDev Execution (ACDE) meeting, where final determinations on the future of the spec will be debated.
Implications for the Ecosystem
The challenge presented by Glamsterdam highlights the inherent tension between protocol evolution and backward compatibility. Ethereum is frequently described as a "world computer" whose most valuable asset is its immutable nature. However, upgrades to the base layer—while necessary to improve throughput and cost-efficiency—can occasionally cause collateral damage to the application layer.
The current situation is particularly sensitive because many affected contracts are immutable; once deployed, their code cannot be patched or upgraded without significant complexity, such as proxy migration or the deployment of new versions. If the core developers proceed with the current specifications, it would force a significant portion of the DeFi ecosystem to either migrate their funds to new, updated contracts or face the risk of total loss. This has led to mounting pressure from the developer community, with many calling for a more rigorous assessment of how protocol changes affect existing codebases before they are finalized.
Addressing the Vulnerability: A Call to Action
In response to these findings, the Ethereum Foundation has initiated a collaborative effort involving internal auditors and third-party firms like Dedaub and Chainsecurity. Recognizing that they cannot manually audit every single contract on the Ethereum mainnet, developers have released a dedicated repository containing the eight specific invariants that will be broken by the Glamsterdam upgrade. This repository serves as a diagnostic tool, allowing project maintainers to test their own code against the proposed changes.
"We cannot cover all projects on Ethereum, especially not their on and off-chain code," a representative noted in the recent call to action. The Foundation is urging contract developers, auditors, and protocol leads to verify their systems immediately and contact the dedicated support team at [email protected] if they identify any potential for breakage.
Looking Toward the November 19th Decision
As the community approaches the November 19th AllCoreDev Execution (ACDE) meeting, the consensus appears to be shifting toward caution. The primary concern is no longer just the technical implementation of the gas changes, but the broader governance process regarding how breaking changes are introduced to the network.
Several potential paths forward are currently being prototyped by the development team:
- Specification Revision: Modifying EIP-8037 and EIP-8038 to accommodate the current gas invariants, potentially sacrificing some optimization for the sake of ecosystem stability.
- Delayed Rollout: Pushing back the hardfork significantly to allow developers time to migrate affected contracts to new, compliant versions.
- Compromise Models: Implementing the changes in a way that provides a "grace period" or dual-gas pricing for a limited window, though this is considered technically complex and carries its own risks.
The findings presented at the November 16th session will be pivotal. This meeting will host representatives from Dedaub, Chainsecurity, and the Ethereum Foundation, providing an open forum for application developers to voice their concerns. The goal is to ensure that when a decision is made on the 19th, it is based on a comprehensive understanding of the impact on the network’s total value locked (TVL) and the security of its constituent protocols.
Industry Context and Future-Proofing
This event underscores the maturation of Ethereum’s development lifecycle. In the early years of the network, updates were often pushed with less focus on the granular impact on every single contract. Today, with billions of dollars in assets secured by smart contracts, the stakes are significantly higher. The industry is watching closely to see if the Ethereum Foundation can strike the right balance between necessary technical innovation and the preservation of the "do no harm" principle that is essential for maintaining institutional trust.
The work on Hegota, a separate development stream within the Ethereum roadmap, continues to proceed in parallel, unaffected by the current bottleneck. This compartmentalization of development efforts is a testament to the organizational resilience of the Ethereum ecosystem, which has successfully navigated previous forks and technical hurdles.
Ultimately, the Glamsterdam delay serves as a reminder that even in a decentralized, permissionless environment, the technical and social layers of a network must work in tandem. By prioritizing the stability of existing contracts over the speed of the upgrade, the Ethereum community is reaffirming its commitment to the long-term integrity of the platform, even at the cost of short-term progress. Whether this results in a watered-down version of the proposed EIPs or a strategic pivot, the upcoming weeks will likely define the protocol’s approach to backward compatibility for years to come.







