Ethereum’s Glamsterdam Upgrade Delayed until May 2027
Ethereum developers have pushed the earliest possible launch of the Glamsterdam upgrade to January 2027, with potential changes to gas pricing rules threatening to delay its rollout until May.
- Updated Timeline: Ethereum’s Glamsterdam upgrade could face delays until May 2027 due to specification changes.
- Outreach: The Ethereum Foundation and security researchers contacted at least 50 affected companies.
- Security Assessment: ChainSecurity reported 200 compatibility findings, including three high-severity cases.
- Proposed Testnet Fork: Developers tentatively proposed December 16 or 17 for the Hoodi testnet fork.
During the November 19 All Core Developers meeting, Ethereum Foundation developer Rahul Kothari stated that the foundation, ChainSecurity, and Dedaub had contacted at least 50 companies affected by the proposed changes.
Initially, developers aimed to activate Glamsterdam on the mainnet in December. However, compatibility issues with applications already running on Ethereum have sparked discussions about revising the upgrade's specifications.
Potential Launch Timelines
Kothari informed developers that three high-severity cases identified during the investigation had been addressed or were expected to be resolved by mid-December. Medium-severity issues have been communicated with completion dates extending to January 10.
With affected companies working on software fixes, mid-January has emerged as the earliest possible mainnet activation window, assuming developers retain Glamsterdam’s existing specifications.
Ansgar Dietrichs, who chaired the meeting, deemed late January or early February a more realistic timeframe. Delaying the decision on specification changes until January could push the rollout to late February or early March, even if developers ultimately maintain the existing rules.
Implementing revised specifications at that stage could delay mainnet activation until April or May, as client teams would require time to integrate and test the changes.
Security Concerns and Assessment
Ethereum researcher Toni Wahrstätter cautioned against introducing modifications without fully understanding their potential impacts on other applications.
"Every spec change could, again, break new invariants that we are not aware of breaking yet," Wahrstätter said during the discussion.
Most execution client teams favored adhering to the existing specifications. Geth, Nethermind, Reth, and ethrex supported retaining the current rules, while Erigon preferred modifications. Besu expressed reservations but indicated it could proceed with the existing approach.
Compatibility Issues and Assessment Results
The compatibility concerns stem from two Ethereum Improvement Proposals (EIPs) that modify how the network calculates fees for operations involving its permanent database:
- EIP-8037: Proposes increasing the cost of creating new state, including deploying smart contracts and adding data to Ethereum’s storage.
- EIP-8038: Addresses the cost of accessing and modifying existing state, arguing that Ethereum’s growing database has made certain operations more resource-intensive since the Berlin upgrade in March 2021.
In a November 18 assessment, ChainSecurity disclosed 200 findings across investigations coordinated by the Ethereum Foundation. Researchers classified three as high severity, 30 as medium, and 167 as low, with none considered critical.
Affected systems include cryptocurrency exchanges, wallets, blockchain bridges, staking protocols, and governance applications.