Ethereum’s Glamsterdam upgrade faces contract-compatibility questions

As reported on November 17, 2026, Ethereum developers had not agreed on how to proceed with the planned Glamsterdam upgrade after a November 16 call about its potential effects on deployed contracts. The upgrade had no confirmed mainnet date.

Ethereum Foundation developer Marius van der Wijden said the upgrade could affect as many as 15,000 on-chain automated programs—far more than earlier reviews had identified. The contracts potentially affected were estimated to involve hundreds of thousands of dollars in funds. These were estimates of possible exposure, not confirmed losses.

Security firm ChainSecurity’s Tanguy Rocher reported 152 findings, about half of which overlapped with the Foundation’s internal research; together, the reviews identified roughly 200 potential issues. In a separate review of about 25,000 contracts with unusual gas usage, Dedaub flagged 70 medium- or high-risk issues, including 22 the Foundation had previously missed. Most issues stemmed from two of the eight core technical assumptions the Foundation had warned developers about on November 6. The Foundation also identified three high-severity and at least 25 medium-severity defects during its external outreach, most of which were being fixed.

Researcher Ansgar Dietrichs, who helped write the proposal, favored continuing with the upgrade but acknowledged that core engineers needed to communicate more clearly with outside developers. Other participants warned that removing EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals.

Compatibility problems had delayed testing since October, including a planned deployment to the Hoodi public testnet. Core developers planned to revisit the proposal at their November 19 meeting. The Foundation said Hoodi would remain on hold until the issues were resolved.