chore: update 31 #293
chore: update 31 #293
Conversation
cips/cip-031.md
Outdated
| @@ -157,6 +157,8 @@ When upgrading to v4 we propose introducing a migration that will set the Parame | |||
|
|
|||
| The continuous and delayed vesting account types will be updated to implement CIP-31. Specifically, they will implement the `UpdateSchedule` function so that the original vesting amount can account for staking rewards. The periodic and permanent account types will not support CIP-31. They will be disallowed from being created. | |||
|
|
|||
| When delegating an account has the option to set another withdraw address, due to rewards needing to adhere to the original vesting schedule the withdraw address must be the same as the delegator address. This is to ensure that the rewards are locked up in the same account. | |||
There was a problem hiding this comment.
When delegating an account has the option to set another withdraw address
I think a user can send MsgSetWithdrawAddress after delegating so perhaps this can be rephrased to:
Accounts can set a withdraw address via MsgSetWithdrawAddress. Due to rewards...
There was a problem hiding this comment.
due to rewards needing to adhere to the original vesting schedule the withdraw address must be the same as the delegator address
How can we enforce this for vesting accounts that have already delegated and set a withdraw address? Perhaps this should be rephrased to say something like: "vesting accounts that have already delegated and set a withdraw address different from the vesting account address will not receive rewards. Instead the vesting account will receive rewards"
Co-authored-by: Rootul P <[email protected]>
Overview
This update is around staking reward withdraw addresses. Due to the requirement that staking rewards must adhere to their vesting schedule it is required to keep the original delegation address as the withdraw address.