Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add support for setting fee-recipient per validator #3820

Closed
philknows opened this issue Mar 2, 2022 · 1 comment
Closed

Add support for setting fee-recipient per validator #3820

philknows opened this issue Mar 2, 2022 · 1 comment
Labels
spec-bellatrix 🐼 Issues targeting the merge spec version.

Comments

@philknows
Copy link
Member

Is your feature request related to a problem? Please describe.

Reference Teku implementation: Consensys/teku#4894
Reference Lighthouse implementation: sigp/lighthouse#2924

Currently, there is no way for a user to set a specific fee-recipient address per configured validator. There will need to be a way for users, especially ones with multiple validators, to specifically set a custom address per validator configured.

The beacon-apis have an endpoint: ethereum/beacon-APIs#178 to accept the fee-recipient of all the known validators to the BN.

Describe the solution you'd like

Teku and Lighthouse both have their own implementations merged already. We should determine which method is the better approach considering complexity and user experience, then implement into our own BN & VC.
@philknows philknows added the spec-bellatrix 🐼 Issues targeting the merge spec version. label Mar 2, 2022
@philknows
Copy link
Member Author

Closing. Duplicate of #3693.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec-bellatrix 🐼 Issues targeting the merge spec version.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@philknows