-
Notifications
You must be signed in to change notification settings - Fork 784
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
Electra updates for v1.5.0-alpha.6 #6445
Conversation
4b7428e
to
65bac11
Compare
aacad31
to
33c1b2c
Compare
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.
Looks good! Almost done reviewing, just gotta do the single pass changes.
beacon_node/execution_layer/src/engine_api/new_payload_request.rs
Outdated
Show resolved
Hide resolved
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!
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!
Just a few minor comments
Co-authored-by: Michael Sproul <[email protected]>
Co-authored-by: Michael Sproul <[email protected]>
Co-authored-by: Michael Sproul <[email protected]>
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 83d5c52 |
* Update process_slashing * Update test vectors version * Delete Domain::Consolidation * Rename to get_max_effective_balance * Fix unused; lint * Add the pre-electra slashing processing * lint * Change request json types * Move requests from payload to beacon block body * Refactor engine api * Fix warnings * Update engine api to latest * engine api changed..again * yet again * Merge branch 'engine-requests' into electra-updates * Fix tests * Store reference instead of bytes in NewPayloadRequest * Merge branch 'unstable' into electra-updates * Update beacon_node/execution_layer/src/engine_api/json_structures.rs Co-authored-by: Michael Sproul <[email protected]> * Update beacon_node/execution_layer/src/lib.rs Co-authored-by: Michael Sproul <[email protected]> * Update beacon_node/execution_layer/src/test_utils/handle_rpc.rs Co-authored-by: Michael Sproul <[email protected]>
Issue Addressed
N/A
Proposed Changes
process_single_slashing
function instead of creating a new function for electra as I think both the pre-electra and electra functions have the same logic. I'm not completely sure if we need to make a separate >= Electra function and keep the pre-electra logic as is.Edit: Confirmed that we need different behaviour for pre and post electra. Modified in
65bac11
get_validator_max_effective_balance
simplify name of helperget_validator_max_effective_balance
ethereum/consensus-specs#3909Remaining spec updates for electra are cosmetic
Blocked on #6435 for EF tests to pass.Merged #6435 into this PR to get the tests passing.