-
Notifications
You must be signed in to change notification settings - Fork 2.6k
nomination-pools: allow pool operators to manage claimable funds #11638
Comments
This sounds like a good improvement to explore! we will look into it. |
Hello @kianenigma, from the issue description I gathered the following.
Taking this on! |
cc @rossbulat please look into this. |
Okay, my thoughts on this are: The only reasonable action for you is that you will allow the pool operator to call This must be entirely optional. Existing pool members should not be affected by this. We can explore doing this with a lazy migration, or else you need to be very careful in how you write the migration for this. Thanks @Doordashcon for taking this on 💯 |
This is a nice addition, but for many users it will be a fun experience to go back to the dashboard on a daily basis and discover and claim how much reward they've received. This also encourages more time on the dashboard & more engagement with the network. So adding this feature, although nice, potentially prohibits this positive user pattern & risks the user forgetting about checking Polkadot in the future. |
Hopefully making this feature optional should mitigate this risk, I also think nominators would want to check the actions of their pool operators from time to time. |
indeed this should be option, and default is current behavior. |
Currently when someone joins a nomination pool they have to actively manage it by claiming rewards or increasing their bond.
From our experience delegators want to stake and forget. Depending on the complexity of the custody this would be a rather big burden.
It would be great if the pool operator could take over this task for their members.
A member could set a default action for claimable funds when joining a pool,
increase_bond
orwithdraw_claimables
and then anyone could trigger the event and pay the transaction fees. This would allow the pool operator to take over this task.@kianenigma mentioned that this should generally be possible to add but for simplicity reasons it was kept the way it is.
This feature would make the staking experience more seamless.
The text was updated successfully, but these errors were encountered: