You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When claiming validator rewards, we’d prefer these rewards not to be directed to a hot wallet(connected to the internet), as they currently are. Instead, it would be ideal to set a designated rewards address so that, upon claiming, the rewards are sent directly to a cold wallet(not connected to the internet), minimizing any risk associated with holding funds in a hot wallet.
A few ideas on how to implement
We could allow setting a rewards address when initing a validator. When you claim rewards, they are sent to this address. This would require validator metadata changes, etc. Not the most flexible approach.
Another approach could be to allow setting the rewards address when running the claim rewards command. This would allow users to switch rewards address per claim if they choose to do so.
Auto restaking rewards at the protocol level should still work as it does today, meaning by setting a rewards address, we do not want all rewards to immediately flow to this address.
The text was updated successfully, but these errors were encountered:
this is already supported. in the cli of claim-rewards, pass --source <address-to-receive-rewards>
nevermind, source is some account where the bond originated from, so it is true we can't withdraw to a diff address
@sug0 I don't think that is true. The source one must provide is the owner of the bond for which rewards are being claimed - it is typically the user who is submitting the tx.
When claiming validator rewards, we’d prefer these rewards not to be directed to a hot wallet(connected to the internet), as they currently are. Instead, it would be ideal to set a designated rewards address so that, upon claiming, the rewards are sent directly to a cold wallet(not connected to the internet), minimizing any risk associated with holding funds in a hot wallet.
A few ideas on how to implement
The text was updated successfully, but these errors were encountered: