-
Notifications
You must be signed in to change notification settings - Fork 765
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 common boilerplate for Berlin hardfork #755
Conversation
Codecov Report
@@ Coverage Diff @@
## master #755 +/- ##
==========================================
- Coverage 92.02% 92.00% -0.02%
==========================================
Files 46 43 -3
Lines 2998 2991 -7
Branches 469 469
==========================================
- Hits 2759 2752 -7
Misses 144 144
Partials 95 95
Continue to review full report at Codecov.
|
"name": "berlin", | ||
"block": null, | ||
"consensus": "poa", | ||
"finality": null |
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.
Just some side note, in case anyone is wondering: these consensus
and finality
fields are from the old Casper/sharding days when it was still planned to do the consensus/finality switches on-chain, modeled this this way to be able to do the respective switches cleanly along the Casper HFs.
So these can very well removed, for the moment this is I guess rather distracting and confusing than anything else.
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.
@holgerd77 Should we remove those fields in this PR or in a separate one?
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.
Think I will merge here now since this is ready-for-merge here anyhow (thanks!). If you want you can open a separate PR on this, not too pressing though.
Great! 😄 I would guess the Kovan network will do this HF as well so I think you can also add the boilerplate code to the The base fees for the opcodes never made it to the These are the only fees from the EIP to take into account I guess? On the VM side you can already add |
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
Part of #736