Skip to content
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

Owner of pool cannot unbond when requirements are met #2052

Open
Juanma0x opened this issue Apr 2, 2024 · 1 comment
Open

Owner of pool cannot unbond when requirements are met #2052

Juanma0x opened this issue Apr 2, 2024 · 1 comment

Comments

@Juanma0x
Copy link

Juanma0x commented Apr 2, 2024

After the nomination pool's state is set to "destroying" and all members have been removed, the owners of nomination pools cannot unbond an amount that would leave the pool below nominationPools.minCreateBond, using the Staking Dashboard.

However, pool owners can still unbond the full amount using the extrinsic nominationPools.unbond. Therefore, the limitation is due to the functionality of the Staking Dashboard.

Ideally, the Staking Dashboard should allow pool owners to unbond the entirety of their funds in the pool when the pool is set to "destroying" and there are no remaining members.

@github-actions github-actions bot added the Stale label Jun 2, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2024
@rossbulat rossbulat reopened this Jun 10, 2024
@github-actions github-actions bot removed the Stale label Jun 11, 2024
@chuacw
Copy link

chuacw commented Oct 3, 2024

Following @Juanma0x 's comment, I was able to unbond using the extrinsic. Unexpectedly, I didn't have to multiply by 10000000000. I entered the exact value of DOT, and I was able to unbond on the Polkadot portal with the extrinsic nominationPools unbond.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants