In the previous weeks Chainsecurity has found a few projects that would be vulnerable after Glamsterdam since they rely on certain invariants. These invariants are broken by EIP-8037 and EIP-8038 which rework how much gas is charged for certain operations and how gas is charged for state.
You can learn more about the details of these potential issues on the Chainsecurity blog post or this tool. Based on these findings, ACD has decided to delay the hardfork process and not fork Hoodi until the issues are resolved.
In order to reach a pragmatic decision on ACD, we need to know what might be broken post-Glamsterdam and if there are any potential spec changes that would prevent these issues. While we are engaging multiple auditing companies, as well as doing internal audits, we can not cover all projects on Ethereum, especially not their on and off-chain code.
Thus, we would like to use this blog as a call for action to contract developers, auditors, etc. to check their projects if they rely on any of these eight invariants. For this purpose we created a repository with invariants that will be broken by Glamsterdam.
It contains a short explanation for the different invariants and examples as well as prompts you can use to verify your own projects.
If you find out that you are affected, please contact us at glamsterdam@ethereum.org.
