Validator client builder support - #10713
Closed
james-prysm wants to merge 23 commits into
Closed
Conversation
james-prysm
marked this pull request as ready for review
May 20, 2022 16:30
james-prysm
requested review from
kasey,
prestonvanloon and
saolyn
and removed request for
a team
May 20, 2022 16:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Feature
related to PR #10669
What does this PR do? Why is it needed?
This PR builds on top of #10669
This PR provides capabilities for users to define fee recipients and gaslimit information on their corresponding validator public keys and send them to the beacon node, which will in turn call the builder APIs. These user-defined configurations are important for custom builders to distribute funds correctly and are signed by the validator key for authenticity. The information used here is similar to the prepare_beacon_proposer APIs which are sent to the execution engine, the register validator API proxies to the builder APIs.
Please refer to the corresponding PRs for additional information
ethereum/builder-specs#2
https://github.com/ethereum/beacon-APIs/pull/209/files