Glamsterdam Testing and Potential Issues
Glamsterdam, the upcoming Ethereum update, is currently undergoing testing on testnets. During these tests, Chainsecurity identified several projects that may be vulnerable after the implementation of Glamsterdam, as they rely on specific invariants. These invariants will be disrupted by EIP-8037 and EIP-8038, which modify the gas charging mechanism for certain operations and state changes.
You can find more details about these potential problems on the Chainsecurity blog post or through this [tool]. Based on these findings, ACD has decided to delay the hardfork process and postpone the fork until the issues are resolved. This delay does not impact the work on Hegota, which continues unabated.
To reach a practical decision in upcoming AllCoreDev calls, it is essential to understand what might be affected post-Glamsterdam and identify any potential spec changes to prevent these issues. We are collaborating with auditing companies Chainsecurity and Dedaub, along with conducting internal audits. However, it is not feasible to cover every project on Ethereum, especially their on- and off-chain code.
Therefore, we are calling on contract developers, auditors, and others to review their projects to determine if they rely on any of these eight invariants. A repository containing a breakdown of the invariants, their explanations, and examples has been created for this purpose. It also includes prompts to help verify your own projects.
If you discover that your project is affected, please reach out to us at.