As reported on November 17, 2026, Ethereum developers had not reached agreement on how to proceed with the planned Glamsterdam upgrade. The comparison at issue was between the upgrade’s intended changes and the behavior of contracts already deployed on Ethereum—not between two live networks.
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, far more than earlier reviews had identified. Funds associated with potentially affected contracts were estimated in the hundreds of thousands of dollars.
The compatibility reviews remained incomplete. ChainSecurity’s Tanguy Rocher reported 152 findings, roughly half of which overlapped with the Foundation’s internal research, for a combined total of 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; 22 had been missed by the Foundation’s earlier work. Most issues stemmed from two of the eight core technical assumptions about which the Foundation had warned developers on November 6. The Foundation also identified three high-severity and at least 25 medium-severity defects in its outreach, most of which were being fixed.
Researcher Ansgar Dietrichs, who helped write the proposal, argued that the upgrade should proceed, while acknowledging that core engineers needed to communicate more clearly with outside developers. Other participants warned that dropping EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals. Those were positions raised in the meeting, not agreed changes.
Compatibility concerns had delayed testing since October and postponed the planned deployment to the Hoodi public testnet. Developers planned to revisit the proposal on November 19. The Foundation said Hoodi would remain on hold until the issues were resolved; no mainnet date for Glamsterdam had been confirmed.