-
Notifications
You must be signed in to change notification settings - Fork 232
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
api: add skip_randao_verification for produceBlockV2 #3837
Conversation
welcome to the bright side - fortunately, it's not that easy to write atrocious Nim code (which perhaps is the main raison d'etre of it), and yours is already looking quite good ;) I guess there are two things to look at here: is the PR good, and is the feature desired in general - I'll focus on the former and then we can have the latter discussion in the spec PR, upon which this PR would depend :) |
@michaelsproul since ethereum/beacon-APIs#222 is merged, we can go ahead with this PR as well as soon as it's rebased / updated to the new param names etc |
57c4d51
to
94a0652
Compare
I've updated this PR to use the |
The relevant location is here: nimbus-eth2/tests/testblockutil.nim Line 99 in 2ad5239
nimbus-eth2/tests/test_blockchain_dag.nim Line 30 in 2ad5239
test in it will do fine.
|
Thanks for the feature and the upstream spec! I'll merge this now and throw in some tests in a separate PR. |
Thanks for having me on as a novice Nimbus contributor! I'll wear the badge with pride 😁 |
Implement ethereum/beacon-APIs#222.
If my Nim isn't too atrocious hopefully I might be able to get this to a mergeable state. I'm putting it up as a draft for gentle feedback (this is my first time ever writing Nim).
Does the broad angle of attack seem acceptable? My next step would be to work out how to put a zero
randao_reveal
in when none is provided, and to add a newUpdateFlag
to disable verification of the RANDAO signature only.