WEB v2: Fee recipient UI #229
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
james-prysm
added
Web V2
rauljordan
approved these changes
Jun 29, 2022
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
Part of #220
What does this PR do? Why is it needed?
This PR introduces new UI features on the Dashboard and Accounts List Page displaying the fee recipient. The Fee Recipient is a post-merge feature that allows users to set an address to get transaction fee rewards from their validators. This new UI feature will allow users to view the fee recipient set for their validator key as well as remove and update for future proposals.
related PR.
prysmaticlabs/prysm#10850
behind the UI the feature uses the keymanager API, a set of standard APIs across client teams.