Ethereum’s Glamsterdam upgrade could be delayed until May 2027 if developers revise its specifications to address smart contract compatibility risks. According to Cointelegraph, the possibility was discussed at Thursday’s All Core Developers meeting, where participants weighed keeping the current design against changes that could reduce risks for some contracts but potentially disrupt others. Glamsterdam is a planned Ethereum hard fork intended to increase network capacity and efficiency. In October, blockchain security firm ChainSecurity warned that proposed gas-pricing changes could disrupt existing smart contracts and potentially expose them to exploitation. Developers subsequently postponed the Hoodi testnet fork, which had been scheduled for Oct. 26. The concerns focus on gas repricing proposals EIP-8037 and EIP-8038. Researchers identified 13 real-world examples of contracts that could be affected in October, while a November investigation examined eight smart contract invariants that might be disrupted. At Thursday’s meeting, developers said the Ethereum Foundation, ChainSecurity and security firm Dedaub had contacted at least 50 affected companies. Three projects were deemed high impact, with fixes completed or expected by mid-December; medium-impact projects reported timelines extending to Jan. 10. One developer cautioned that changes to specifications could break other invariants that developers had not yet identified.
Under the existing specifications, Glamsterdam could activate on mainnet as early as mid-January 2027. However, if developers wait until January to decide whether to make changes, activation could move to late February or early March. Adopting modifications could push the upgrade further, to April or May, and developers have not reached a decision. Separately, Ethereum developers are considering reducing the scope of Hegotá, the network’s next planned hard fork, to accelerate its transition to post-quantum cryptography. During the meeting, participants discussed postponing some Ethereum Improvement Proposals to prioritize post-quantum features. Several developers argued that narrowing the upgrade’s scope would have limited value unless it also shortened the rollout timeline. Participants also raised compatibility concerns about EIP-8151, a proposal intended to protect accounts moving to post-quantum security. A preliminary review found that a potentially large number of existing smart contracts could be affected, creating uncertainty about including the proposal in Hegotá. Developers made no decision on the fork’s scope. Client teams are expected to provide their positions before further discussions in two weeks.
