Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

Glamsterdam Compatibility Review Flags Risks for On-Chain Automation

As reported on November 17, 2026, Ethereum developers had not reached agreement on how to proceed with the planned Glamsterdam upgrade after a compatibility review identified a potentially wider impact than earlier checks had found. The Hoodi public testnet deployment remained on hold, and there was no confirmed mainnet timetable.

At a November 16 developer call, Ethereum Foundation developer Marius van der Wijden said the upgrade could affect as many as 15,000 on-chain automation programs. The funds associated with potentially affected contracts were estimated at hundreds of thousands of dollars. Both figures describe a potential impact, not confirmed losses or a final count of incompatible contracts.

The reviews produced overlapping findings. ChainSecurity’s Tanguy Rocher reported 152 findings, roughly half of which overlapped with the Foundation’s internal research; together, the work identified about 200 potential issues. In a separate review of approximately 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 about which the Foundation had warned developers on November 6. The source did not specify which two assumptions.

The Foundation also identified three high-severity and at least 25 medium-severity defects through its external communication with developers; most were being fixed. These counts come from different review efforts and should not be treated as a single, non-overlapping total.

The proposed path forward remained contested. Researcher Ansgar Dietrichs, who helped write the proposal, argued for continuing with the upgrade while acknowledging that core engineers needed to communicate more clearly with external developers. Other meeting participants warned that removing EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals. That was their assessment of a possible change, not a decision to remove the proposal.

Compatibility concerns had delayed testing since October and pushed back the planned Hoodi deployment. Developers planned to revisit the proposal at a November 19 meeting. The Foundation said Hoodi would remain on hold until the issues were resolved.