-
Notifications
You must be signed in to change notification settings - Fork 782
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
Add arrowGlacier HF #1527
Add arrowGlacier HF #1527
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
For reference: ethereum/tests#965 ( |
For reference: ethereum/tests#972 (new difficulty tests on |
I guess at some point we should also get over the finish line with this. Any updates here? What's the current status? 🤔 |
If we want we can merge this and then at a later point run it against ethereum/tests? I can try running the test locally to see if they pass, if thats the case then we can also merge. |
Ok, maybe let's then wait for the official @jochem-brouwer Can you do rebase in between and bring this up-to-date so that we can keep up here a bit with keeping this close to |
Will |
bc7b386
to
61486bb
Compare
Ok this is weird, the tests do not pass, I tried locally. To test;
This pulls the latest data from the repo, the difficulty tests are not added yet. Now to
Only running these tests;
|
Yes, can confirm. Also ran this locally, when digging a bit deeper one sees that every second test with Not sure yet what is happening, the format of this uncles field changed substantially (there was a full hash before), will ask on |
The semantics of the If one is replacing Will push. |
bad01f1
to
7807f02
Compare
@holgerd77 I see, but I don't understand how this passes. I don't see anything in your commits which handles this (Small sidenote: we should at some point make these block tests not use the copied JSON files from ethereum/tests, but directly read them from ethereum/tests) |
Yes, edited test file. |
Ah right. We should fix that at some point, I don't think it is so hard, seems like the difficulty formula is adjusted if either the uncle hash is the empty RLP list hash OR it is not, so we could just create a bogus hash which should (?) not crash the difficulty calculation. Will approve here. |
Oh right, I can't approve my own PR 😂 |
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 and x-approved by @jochem-brouwer, will merge.
This PR adds the arrow glacier HF, which delays the difficulty bomb.
Since we have no test cases, do not merge yet.