Ethereum Delays Glamsterdam Hardfork Over Gas Calculation Vulnerabilities
Developers urged to audit smart contracts against new gas cost invariants.
1Glamsterdam Hardfork Postponed
The Ethereum All Core Developers (ACD) group has officially decided to delay the upcoming Glamsterdam hardfork. This decision follows critical findings by Chainsecurity regarding potential vulnerabilities. The fork will not proceed until developers resolve issues arising from changes to how gas is charged for specific operations and state storage mechanisms.
2Gas Calculation Changes
EIP-8037 and EIP-8038 introduce significant modifications to Ethereum's gas pricing model. These updates alter the costs associated with specific operations and state management. While intended to optimize network efficiency, these adjustments inadvertently break existing invariants that many smart contracts currently rely upon for their operational security and logic.
3Chainsecurity Vulnerability Findings
Recent audits conducted by Chainsecurity identified several projects that would become vulnerable immediately following the Glamsterdam implementation. These projects depend on specific gas-related invariants that are no longer valid under the new EIP specifications. The firm has documented these risks to help the broader developer community understand the potential impact.
4Call for Community Audits
Ethereum developers and auditors are now urged to conduct thorough reviews of their smart contracts. Because the network is too vast for internal teams to audit every on-chain and off-chain component, the community must take proactive steps. Developers should verify if their code relies on any of the eight identified broken invariants.
5Available Verification Tools
To assist with this transition, a dedicated repository has been created containing detailed explanations of the affected invariants. This resource includes concrete examples and specific prompts that developers can use to test their own projects. Utilizing these tools is essential for identifying potential failures before the hardfork is eventually rescheduled.
6Reporting Identified Risks
If developers discover that their projects are affected by the proposed gas changes, they are requested to contact the core team directly at [email protected]. This communication channel is vital for gathering data on the scope of the issue and determining if further specification changes are required to prevent widespread contract failures.
7Pragmatic Decision Making
The ACD is prioritizing a pragmatic approach to ensure network stability over rapid deployment. By engaging multiple auditing firms and soliciting community feedback, the team aims to identify if any spec adjustments can mitigate these risks. This collaborative process is necessary to maintain the integrity of the Ethereum ecosystem post-fork.
8Future Network Stability
The delay highlights the complex relationship between protocol-level gas changes and application-layer security. As Ethereum evolves, maintaining backward compatibility while introducing optimizations remains a significant challenge. The success of the Glamsterdam upgrade now depends on the collective effort of the developer community to secure their contracts against these fundamental changes.