-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nimbus t8n forkname+xxxx eip support #1607
Comments
We have an open PR #1401 exploring this possibility, but then I realize something that is very difficult to solve. Nimbus EVM opcode dispatcher is generated during compiletime, not at runtime. And the instruction table is generated for every hard fork. Runtime modification to this table is very difficult, because the static table need to be converted into a dynamic table, and the optimized codegen(to C) will dissapear. |
This feauture is not mandatory. |
Due to technical reason, this feature will not be implemented in nimbus-eth1. |
Has Nimbus implemented eip1153?
Sometimes before the inclusion we use this schema Shanghai+1153 to tell that 1153 is to be activated on top of Shanghai rules.
This is because we don't know if 1153 is gonna be in Merge or Shanghai or Cancun
so the t8n allows to generate the tests for 1153 using the latest evm revision (Shanghai for instance)
And then when it is included we just rename it to Shanghai.
This is not possible for all eips but some.
The text was updated successfully, but these errors were encountered: