Glamsterdam, the subsequent replace for Ethereum, is at the moment being examined on testnets.
Throughout these assessments Chainsecurity has discovered just a few initiatives that might be weak after Glamsterdam since they depend on sure invariants. These invariants will probably be damaged by EIP-8037 and EIP-8038 which rework how a lot fuel is charged for sure operations and the way fuel is charged for state.

You’ll be able to study extra concerning the particulars of those potential points on the Chainsecurity weblog publish or this device. Based mostly on these findings, ACD has determined to delay the hardfork course of and never fork Hoodi till the problems are resolved. Throughout this delay, the work on Hegota shouldn’t be affected and is continuous in parallel in full drive.

With a purpose to attain a practical resolution on the subsequent AllCoreDev calls, we have to know what is likely to be damaged post-Glamsterdam and if there are any potential spec modifications that might forestall these points. We’re partaking the auditing corporations Chainsecurity and Dedaub, in addition to doing inside audits. Nonetheless we can’t cowl all initiatives on Ethereum, particularly not their on and off-chain code.

Thus, we wish to use this weblog as a name for motion to contract builders, auditors, and so forth. to test their initiatives in the event that they depend on any of those eight invariants. For this function we created a repository with invariants that will probably be damaged by Glamsterdam.

It accommodates a brief clarification for the totally different invariants and examples in addition to prompts you need to use to confirm your individual initiatives.

Should you discover out that you’re affected, please contact us at glamsterdam@ethereum.org.

Replace (Nov. ninth 2026)

Since Friday’s publish, we’ve acquired 4 stories figuring out deployed contracts that would break underneath the proposed modifications in EIP-8037 and EIP-8038. Thanks to everybody who despatched an instance. We’re reviewing every report and contacting protocols which may be affected.

We’ve additionally heard a broader concern that any modifications affecting deployed, immutable contracts aren’t getting the scrutiny they deserve. We’re contemplating these issues significantly. We advocate that ACD waits till the audit findings are public and there was time to assessment them earlier than deciding whether or not to revise the specs or when to schedule the Hoodi improve.

If the findings present that the affect on deployed contracts is simply too widespread to just accept, ACD may revise the specs. Work is already underway to prototype and assessment a number of potential revisions. We’re documenting which issues every revision would tackle and which different invariants spec modifications may break to current on ACDE on 19 November.

Should you suppose it’s possible you’ll be affected, test the invariants repository and make contact with us at glamsterdam@ethereum.org. Public stories are learn too.