-
Notifications
You must be signed in to change notification settings - Fork 753
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
common: handle forkHash on timestamp == genesis timestamp #2959
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
Co-authored-by: g11tech <gajinder@g11.in>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Great find! This is a relatively sensitive change and can have side effects on other girl hash calculations, I would feel better with 1-2 dedicated test cases for it. |
Yes, you are right, especially these "small" changes can be tested quickly with small tests. I will add tests. For a general comment though, some hive tests are very complex and would take long to integrate - what we could do (mid-term) is to create a hive CI runner and then run these specific tests to cover these test cases (and for a bonus: also include this into codecov, but that would be complex since we need to hook into hive's docker image of our client) |
Fixes:
./hive --sim "ethereum/engine" --client ethereumjs --sim.parallelism 16 --sim.limit="engine-cancun/Request Blob Pooled Transactions"
If fork is at timestamp genesisTimestamp then this fork is supposed to be active at timestamp = 0 and not participate in the forkHash calculation of the devp2p/ETH STATUS message.
See also:
hyperledger/besu#5744
ethereum/go-ethereum#27895
https://eips.ethereum.org/EIPS/eip-6122