-
Notifications
You must be signed in to change notification settings - Fork 518
clients/erigon: enable commitment history #1355
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
base: master
Are you sure you want to change the base?
Conversation
|
I'm curious, which tests are these? The rpc-compat tests really should not require any special settings in the client. |
|
For example, they are Anyway, commitment history in Erigon is currently experimental only because it's a recent addition, so it won't be special in the near future 🙂 |
|
The requirement for archive node in tests is not intentional, that's why I'm asking. I want the tests to be runnable in the node's default configuration if at all possible. For the tests you mention, we can definitely change |
I completely understand this. We can remove any non-intentional archive requirement by moving the tests on newer blocks, as you suggest.
OK that's fine with me. We could also consider moving forward I can try to contribute on this by issuing a PR in https://github.com/ethereum/execution-apis repo next week, if you agree. |
Restore ethereum/hive usage in our CI since it's important to run against it by allowing 8 failures for `rpc-compat`. See ethereum/hive#1355 for open discussion on how to solve such failures.
Restore ethereum/hive usage in our CI since it's important to run against it by allowing 8 failures for `rpc-compat`. See ethereum/hive#1355 for open discussion on how to solve such failures.
Add flag to enable commitment history in Erigon: this is necessary to fix some failing
rpc-compattests which require historical state root computation