Keymanager APIs: fee recipient api #10850
Merged
Conversation
This file contains 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
Co-authored-by: Radosław Kapka <[email protected]>
Co-authored-by: Radosław Kapka <[email protected]>
rkapka
reviewed
Jun 16, 2022
rkapka
approved these changes
Jun 16, 2022
rauljordan
approved these changes
Jun 16, 2022
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #10292
What does this PR do? Why is it needed?
This PR adds the get, post, and delete APIs as specified by the keymanager APIs. This will allow users to update a fee recipient for a given validator public key. This api activated in prysm via the
--webcommand and works similar to other keymanager APIs.note: the fee recipient is updated in the validator client but will update on the beacon chain/builder only during the set intervals ( when the validator client turns on, when a validator key becomes active, or at the beginning of an epoch)