Developers weigh specification changes
Ethereum developers debated Glamsterdam’s smart contract compatibility risks at an All Core Developers meeting on Thursday, according to Cointelegraph. They considered whether to retain the upgrade’s existing specifications or modify them to reduce those risks.
Developers said the Ethereum Foundation, ChainSecurity and security firm Dedaub had collectively contacted at least 50 affected companies, Cointelegraph reported. The discussion did not produce a decision: changes intended to protect some contracts could disrupt others.
Compatibility concerns have prompted scrutiny
The concerns center on proposed changes to Ethereum’s gas pricing. ChainSecurity warned in October that they could disrupt existing smart contracts and potentially expose them to exploitation, Cointelegraph reported. The warning prompted developers to postpone the Hoodi testnet fork, which had originally been scheduled for Oct. 26.
Cointelegraph also reported that researchers identified 13 real-world examples of potentially affected contracts in October, and that a November investigation examined eight smart contract invariants the upgrade could disrupt. These reports describe potential effects, not confirmed disruption across all affected contracts.
In the report’s account of the outreach, three projects were classified as high impact, with fixes completed or expected by mid-December. Medium-impact projects reported timelines extending to Jan. 10. The source does not establish that every project had completed its fixes.
Activation dates remain conditional
Cointelegraph’s Nov. 19 publication reported that Glamsterdam could be pushed back as far as May 2027 if developers decide to modify its specifications. Under the current specifications, mainnet activation could come as early as mid-January 2027.
The report said that waiting until January to decide could move activation to late February or early March, or to April or May if modifications are adopted. These are conditional projections, not a confirmed change to the schedule; developers had not reached a decision.