-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[staking] Currency Migration and Overstake fix #7763
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
Conversation
|
/cmd prdoc |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look sane but a disclaimer - I'm not very familiar with this topic.
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-7763-to-stable2407
git worktree add --checkout .worktree/backport-7763-to-stable2407 backport-7763-to-stable2407
cd .worktree/backport-7763-to-stable2407
git reset --hard HEAD^
git cherry-pick -x f540d2b3d26d24a952e792cdae05bb89c43e5173
git push --force-with-lease |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-7763-to-stable2409
git worktree add --checkout .worktree/backport-7763-to-stable2409 backport-7763-to-stable2409
cd .worktree/backport-7763-to-stable2409
git reset --hard HEAD^
git cherry-pick -x f540d2b3d26d24a952e792cdae05bb89c43e5173
git push --force-with-lease |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-7763-to-stable2412
git worktree add --checkout .worktree/backport-7763-to-stable2412 backport-7763-to-stable2412
cd .worktree/backport-7763-to-stable2412
git reset --hard HEAD^
git cherry-pick -x f540d2b3d26d24a952e792cdae05bb89c43e5173
git push --force-with-lease |
## Summary The existing fungible migration code has an issue when handling partially unbonding accounts, leaving them in an inconsistent state. These changes fix it by properly withdrawing overstake from unlock chunks. This PR also removes the `withdraw_overstake` extrinsic from pallet-staking, as this scenario could only occur before the fungible migration. With fungibles, over-staking is no longer possible. ## TODO - [ ] Backport to stable2503. --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> (cherry picked from commit f540d2b)
|
Successfully created backport PR for |
Backport #7763 into `stable2503` from Ank4n. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot. <!-- # To be used by other automation, do not modify: original-pr-number: #${pull_number} --> Co-authored-by: Ankan <[email protected]>
## Summary The existing fungible migration code has an issue when handling partially unbonding accounts, leaving them in an inconsistent state. These changes fix it by properly withdrawing overstake from unlock chunks. This PR also removes the `withdraw_overstake` extrinsic from pallet-staking, as this scenario could only occur before the fungible migration. With fungibles, over-staking is no longer possible. ## TODO - [ ] Backport to stable2503. --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Summary
The existing fungible migration code has an issue when handling partially unbonding accounts, leaving them in an inconsistent state. These changes fix it by properly withdrawing overstake from unlock chunks.
This PR also removes the
withdraw_overstakeextrinsic from pallet-staking, as this scenario could only occur before the fungible migration. With fungibles, over-staking is no longer possible.TODO