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.

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

Handle fee recipients for the different DVT/LSD protocols #186

Open
dsimog01 opened this issue Feb 22, 2023 · 1 comment
Open

Handle fee recipients for the different DVT/LSD protocols #186

dsimog01 opened this issue Feb 22, 2023 · 1 comment
Labels
Needs research This issue requires research open to discussion This issue is open to discussion and brainstorming P1 Medium priority

Comments

@dsimog01
Copy link
Contributor

We need to handle the fee recipients for the protocols that need a fix address for this field. For example, rocketpool asks all the users to have the same fee recipient, but others depend on the pool in which the user participates. Some others might also give more flexibility on this topic.

We should research how each of these work in order to allow the automatic import via launchpad API of the brain. One option to consider is to use a validator pubkey to get the fee recipient associated to it, but his may not be available for all the protocols

@dsimog01 dsimog01 added P1 Medium priority Needs research This issue requires research open to discussion This issue is open to discussion and brainstorming labels Feb 22, 2023
@dsimog01
Copy link
Contributor Author

Fee recipients Changeable? How to handle from backend? Value
Rocketpool No
Stakehouse
Stakewise v3
Solo
Obol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs research This issue requires research open to discussion This issue is open to discussion and brainstorming P1 Medium priority
Projects
None yet
Development

No branches or pull requests

1 participant