Estimate Puts Ethereum Contracts Potentially Affected by Glamsterdam Upgrade at 10,000–15,000
Key Facts
Ethereum developers estimated that changes in the Glamsterdam upgrade could affect about 10,000–15,000 contracts out of 90 million, according to a summary of their November 16 meeting. The figure describes a potential scope of impact and does not mean that this number of contracts has already been disrupted. Concerns center on proposals EIP-8037 and EIP-8038, which reprice gas for certain operations and change how it is calculated for operations tied to network state. The meeting summary said the estimate refers to contracts that could be affected by these changes, as developers continue to examine audit findings. The issue matters for deployed application projects, which may rely on technical assumptions that will change under the new gas calculation rules.
The Ethereum Foundation said ChainSecurity had identified projects that could become vulnerable to problems after the upgrade because they rely on technical invariants that would change under the proposals. The company’s report explained that a change in the amount of gas available to a contract after a failed call could alter the outcome of its failure-handling path, even if the code remains unchanged. ChainSecurity wrote that "A failure path that previously reverted may now complete, even when the contract code has not changed." The foundation said developers should check whether their projects rely on any of the eight invariants that could be affected by the changes. A change in path behavior could mean a deployed contract needs modification or a review of how it handles a failed call.
Audit findings cited in the November 16 meeting summary show the scope of the review, with figures varying across studies. ChainSecurity identified 152 findings, 76 of which overlapped with the foundation’s internal research, bringing the stated total after accounting for overlap to 200 findings. Dedaub’s study identified about 25,000 contracts with unusual gas patterns and recorded 70 medium- to high-risk findings. The summary said 22 contracts from that study had not appeared in the foundation’s internal research. These findings put the challenge in identifying which contracts require action: an unusual gas pattern or an audit finding alone does not prove that a network failure has occurred.
The foundation said in an earlier update that it had received four reports about deployed contracts that could break under the proposed changes, and that it was reviewing the reports and contacting the protocols concerned. In August, it said replaying historical transactions on mainnet had produced four practical outcomes, ranging from no change to the possibility of a failure. The foundation said at the time that most observed cases could be fixed by increasing the gas limit, and that most contracts were unaffected. It also said it had begun contacting the most exposed teams directly. This provides context for the broader estimate discussed at the November meeting, while the number of contracts potentially affected remains under review.
The foundation says gas repricing is intended to bring gas costs closer to the actual work required by operations, and is a prerequisite for safely raising the gas limit as the network grows. Gas prices for state operations were last adjusted in the Berlin upgrade in 2021, according to the foundation. EIP-8037 and EIP-8038 aim to reset charges for certain operations and the way gas tied to network state is calculated. But changing these rules could affect software invariants relied on by existing contracts, explaining why the audit focuses on compatibility and expected contract behavior. The foundation’s August tests showed that outcomes are not limited to failures; they also include transactions succeeding with differences or requiring a higher gas limit.
In light of these risks, developers paused the upgrade process and postponed Glamsterdam activation on the Hoodi test network until the discovered issues are addressed, according to the Ethereum Foundation. Work on the Hegota upgrade is continuing in parallel, the foundation said. Sepolia had been scheduled for activation on October 6, 2026, while no activation date had been set for Hoodi or mainnet in the foundation’s earlier announcement. Hoodi’s postponement alone does not settle the fate of the upgrade specifications; the foundation said developers could revisit them if the impact on deployed contracts proves unacceptably broad. Teams have also begun preparing prototypes of potential changes.
Ethereum developers are scheduled to discuss the findings and possible next steps at an ACDE meeting on November 19, according to the foundation’s schedule. The foundation said no decision has been set in advance of the meeting, leaving open the possibility of revising the specifications depending on what the findings show. Teams are already working on prototypes of potential alternatives, according to the foundation’s update. The schedule does not determine in advance whether developers will change the proposals or continue with the current version after addressing the issues. Reviewing the changes’ impact on deployed contracts remains central to the next discussion.