-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Further examine necessity of clipping on withdrawals #3041
Comments
Possibly this is addressed by #2958. |
Sure we ought to specify this better in new docs. In the Dec=>Int PR we always ensure that the validator will be emptied aka we do not burn tokens ever. |
My concern is as to why this was happening in the first place - seems like some delegator must have previously received more tokens than they ought to have (which is very concerning). |
What's happening in Jae's PR is not completely obvious to me, however in the Dec=>Int PR there is a clear situation which gives rise to a delegator share being "worth" an uneven amount of tokens THUS when they withdraw, the remaining tokens should be left in the validator, making all the other delegator shares now worth slightly more |
Is this closed by F1? |
No, this has nothing to do with fee distribution, the "withdrawal" referred to is withdrawal of tokens from a validator (in the staking module). |
Do we even clip any more? - during the Dec=>Int this has been consolidated to 1 or 2 straight forward places |
@rigelrozanski thats a great question! |
Just investigated this... within staking clipping is isolated to the cosmos-sdk/x/staking/types/validator.go Lines 370 to 384 in b5e245f
I think it's pretty straightforward why this needs to happen, under the situation that slashing caused delegator's shares to be worth an uneven amount of tokens. Again we are rounding at the nano-atom level. I'm confident that this is correct and no reason for concern. |
Ref https://github.com/cosmos/cosmos-sdk/pull/3033/files#r239978938
The text was updated successfully, but these errors were encountered: