Glamsterdam, the following replace for Ethereum, is at the moment being examined on testnets.
Throughout these checks Chainsecurity has discovered a number of tasks that may be susceptible after Glamsterdam since they depend on sure invariants. These invariants might be damaged by EIP-8037 and EIP-8038 which rework how a lot gasoline is charged for sure operations and the way gasoline is charged for state.
You possibly can study extra in regards to the particulars of those potential points on the Chainsecurity blog post or this tool. Primarily based 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 just isn’t affected and is constant in parallel in full power.
With a purpose to attain a realistic determination on the following AllCoreDev calls, we have to know what may be damaged post-Glamsterdam and if there are any potential spec modifications that may forestall these points. We’re partaking the auditing corporations Chainsecurity and Dedaub, in addition to doing inner audits. Nonetheless we cannot cowl all tasks 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 verify their tasks in the event that they depend on any of those eight invariants. For this function we created a repository with invariants that will be broken by Glamsterdam.
It accommodates a brief rationalization for the completely different invariants and examples in addition to prompts you need to use to confirm your individual tasks.
When you discover out that you’re affected, please contact us at glamsterdam@ethereum.org.
