Polkassembly Logo

Create Pencil IconCreate
OpenGov

Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Discussion

Stuck DOT: Pool Depositor Blocked by Unmigrated Members (Seeking Solutions and Community Input)

userPINKPOOL254
9 months ago
DeFi
pool
migrate
migration
staking

After setting my nomination pool to Destroying and waiting the full 28-day unbonding period, I was able to unbond most members' funds (note: with the current setup all members of the pool must be fully unbonded and have their funds withdrawn prior to the pool creator withdrawing their own funds). The issue is that there is still a few members in the pool that haven't unbonded yet and I can't unbond them myself, even as the pool creator / depositor because they have not yet migrated after the recent Polkadot update. This means that anyone currently running a pool no matter how small that was forced to make a minimum deposit of 500 dot to create the pool will not be able to ever withdraw their own funds from the pool if there is anybody in their pool who hasn't migrated yet, even if that non-migrated member only has 1 dot staked in your pool it will hold your deposit hostage. This is bad because it allows a single inactive member to permanently lock the pool creator’s entire 500+ DOT deposit, not only punishing the depositor but also harming the broader Polkadot economy by reducing staking efficiency, locking valuable capital, and discouraging participation in nomination pools

What small pool creator would be incentivized to start a pool knowing there's a high risk their 500 DOT minimum deposit could be locked indefinitely due to a single inactive member?

Problem Summary:
Pool is in Destroying state

Most member funds successfully withdrawn

A few members have not unbonded or migrated

Depositor cannot withdraw their own funds

No way to force or permissionlessly unbond these inactive accounts

Expected Behavior:
There should be a way for the depositor to finalize pool destruction and recover their stake after a reasonable timeout or if a member is inactive for an extended period.

Proposed Solutions:

1. Allow for dual staking again

2. Allow depositor to force unbonding of inactive members after a defined delay

3. Auto-remove inactive members after X days in Destroying state

4. Permit depositor withdrawal once majority of pool is cleared

**I want to submit a proposal that would allow pool creators to fully destroy their pool even if they have some unmigrated members in their pool and I was wondering if anyone with technical knowledge could suggest the best proposal for this. I have provided some ideas above, your feedback would be much appreciated!

Comments (0)

PleaseLogin to comment

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2026

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy