Glamsterdam, the subsequent replace for Ethereum, is at the moment being examined on testnets.
Throughout these exams Chainsecurity has discovered a couple of initiatives that may be susceptible 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 may study extra in regards to the particulars of those potential points on the Chainsecurity weblog submit 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 pressure.
To be able to attain a realistic choice on the subsequent AllCoreDev calls, we have to know what could be damaged post-Glamsterdam and if there are any potential spec adjustments that may forestall these points. We’re partaking the auditing firms Chainsecurity and Dedaub, in addition to doing inside audits. Nonetheless we cannot cowl all initiatives on Ethereum, particularly not their on and off-chain code.
Thus, we want to use this weblog as a name for motion to contract builders, auditors, and many others. to test their initiatives in the event that they depend on any of those eight invariants. For this goal we created a repository with invariants that will probably be damaged by Glamsterdam.
It comprises a brief rationalization for the completely different invariants and examples in addition to prompts you should utilize to confirm your personal initiatives.
In case you discover out that you’re affected, please contact us at glamsterdam@ethereum.org.
