Ethereum’s upcoming Glamsterdam hard fork could see its mainnet deployment pushed back as far as May 2027 if developers ultimately decide to modify its technical specifications to mitigate critical smart contract compatibility risks. The potential timeline adjustment emerged during discussions at the All Core Developers meeting, highlighting the complex balancing act developers face between introducing major network enhancements and safeguarding the vast ecosystem of decentralized applications built on top of the blockchain.
Glamsterdam is meticulously planned as a major Ethereum hard fork designed with the primary objective of increasing the network’s overall transaction capacity and operational efficiency. However, the path to implementation has encountered notable roadblocks. Blockchain security firm ChainSecurity issued a stark warning in October, indicating that proposed modifications to Ethereum’s gas pricing mechanisms could critically disrupt existing smart contracts. These disruptions could inadvertently expose established protocols to exploitation and unexpected financial loss. This security alert prompted core developers to postpone the Hoodi testnet fork, which had been originally scheduled for October 26, to allow for a more thorough risk assessment.
At the heart of the current concerns are gas repricing proposals designated as Ethereum Improvement Proposal 8037 (EIP-8037) and Ethereum Improvement Proposal 8038 (EIP-8038). Security researchers initially identified 13 real-world examples of potentially affected smart contracts back in October. Subsequent investigations conducted in November cast an even wider net, examining eight distinct smart contract invariants that could be disrupted or completely invalidated by the implementation of the upgrade.
During Thursday’s meeting, developers provided updates on mitigation efforts, noting that the Ethereum Foundation, alongside security firms ChainSecurity and Dedaub, had collectively reached out to at least 50 affected companies to warn them of the potential vulnerabilities. Out of those organizations, three specific projects were classified as high impact. Fortunately, fixes for these high-impact projects have either been completed or are expected to be fully implemented by mid-December. Meanwhile, projects categorized as medium impact have reported remediation timelines stretching out to January 10.
Despite these remediation efforts, developers spent a significant portion of the meeting debating whether to retain Glamsterdam’s existing specifications as originally drafted or to modify them in an attempt to reduce broader compatibility risks. The dilemma is compounded by the delicate nature of blockchain upgrades: alterations intended to protect certain classes of smart contracts could inadvertently disrupt others, creating a game of technical whack-a-mole.
"Every spec change could, again, break new invariants that we are not aware of breaking yet," one developer warned during the meeting, capturing the cautious sentiment shared across the development community.
Under the current, unmodified specifications, mainnet activation for Glamsterdam could come as early as mid-January 2027. However, if developers opt to wait until January to reach a definitive consensus on how to proceed, that decision-making delay could push activation back to late February or early March. Furthermore, if modifications to the specifications are ultimately adopted to address the contract risks, the deployment timeline could stretch even further into April or May 2027. As of the conclusion of the meeting, no final decision has been officially reached.
Ethereum Weighs Accelerating Post-Quantum Security
In a separate development concerning the network’s long-term roadmap, Ethereum’s subsequent planned hard fork, known as Hegotá, could see its overall scope significantly reduced as the core development team seeks to accelerate the network’s transition to post-quantum cryptography.
During the same meeting, developers actively considered postponing several Ethereum Improvement Proposals currently slated for Hegotá in order to prioritize the integration of post-quantum features. While preparing the network for a future where quantum computers could potentially crack current cryptographic standards is viewed as an existential necessity, opinions remained divided. Several participants argued that simply reducing the upgrade’s scope would offer very little practical benefit unless the reduction also succeeded in shortening the overall rollout timeline for the network.
Adding to the complexity, developers also raised pressing compatibility concerns regarding Ethereum Improvement Proposal 8151 (EIP-8151). This specific proposal is designed to protect user accounts as they migrate toward post-quantum security standards. However, a preliminary technical review identified a potentially large number of existing smart contracts that could be negatively affected by the proposed changes, thereby complicating the proposal’s inclusion in the upcoming Hegotá fork.
Ultimately, no final decision was reached regarding the definitive scope of the Hegotá upgrade. Client teams are now expected to formally submit their individual positions and recommendations ahead of further discussions scheduled to take place in two weeks.
