Ethereum has ruled out activating its next major protocol upgrade, Glamsterdam, in December as planned. The reason is to have enough time to fix smart contracts. Developers see late January or early February 2027 as the most realistic date to deploy the upgrade on the mainnet if they keep the current specifications.
What can go wrong with Glamsterdam
The delay will give time to projects affected by changes in the cost of executing certain operations. If developers decide to modify those rules, activation could slip to April or May, according to the scenarios discussed on November 19.
The Ethereum Foundation, ChainSecurity and Dedaub have contacted at least 50 companies that have confirmed the changes affect them, explained Rahul Kothari of the Ethereum Foundation. The three high-severity cases had already been stabilized or were expected to be by mid-December. For the medium-severity ones, the latest deadline reported before the meeting was January 10.
That is why Kothari placed the first viable date in mid-January and why Ansgar Dietrichs, who chaired the meeting, pointed to late January or early February.
Cybersecurity
Proposals EIP-8037 and EIP-8038 change the gas cost of creating and querying data that Ethereum stores persistently. The most common problem arises when a contract has a fixed amount of gas assigned to an operation. If the new cost exceeds that limit, the operation can fail even if the contract code remains the same. The Ethereum Foundation explained on November 6 that it had halted deployment on the Hoodi testnet to assess that impact.
200 findings
ChainSecurity's assessment includes 200 findings: three high severity, 30 medium severity and 167 low severity. Most can be resolved with configuration adjustments, but 24 require updating or migrating contracts. Among the systems analyzed are wallets, cross-chain bridges, exchange platforms and staking protocols. The report identifies possible operation disruptions, frozen funds and errors in reward calculations.
Most of the teams maintaining the execution software leaned toward keeping the current rules. Dietrichs proposed activating Glamsterdam on Hoodi on December 16 or 17, subject to the decision of the November 26 consensus meeting. Teams in favor of changing the specification have until that meeting to present a concrete proposal with an impact analysis.
Lido also asked for room to adapt its protocol. Dima Gusakov, technical lead for staking modules at Lido Labs, asked that Glamsterdam be activated no earlier than late January to allow time for Lido's governance vote.