Hi! This proposal is to free up KSM that got stuck due to the corrupted staking state. Builders guys suggested this as the only way. Thanks!

The utility.batchAll call combines two extrinsics: 

1. Kill_storage that will delete the ledger set storage
2. Calling force_unstake will move locked KSM to the transferable state

The address HHJrycDzgkRqQpw5oWUw7iGQMppuNud6LkQdtkxPXhiWQ5i has the controller set and included in the bonded storage (see screenshot) but then GKycVDHctU5wzkvUoYQLNr8a1wtJQzCwY8tfRTBYK52mHLF was not added to the ledger storage.

@[@amitrovich](https://kusama.polkassembly.io/user/amitrovich) there is no screenshot. Can you please share this?

According to Parity, staking.ledger.claimedRewards was moved from Vec<_> to BoundedVec<_> in the 9.30 release and this account was somehow the only one among all polkadot and kusama which for some reason had a value that did not respect the bound, therefore it cannot be decoded, therefore the chain thinks that this controller has no ledger associated with it.

Confirming what [@amitrovich](https://kusama.polkassembly.io/user/amitrovich) said. 

`StakingLedger.claimed_rewards` is a bounded vec expected to have a maximum count of 84 entries. The account `HHJrycDzgkRqQpw5oWUw7iGQMppuNud6LkQdtkxPXhiWQ5i` however ended up with 85 entries because of an old migration bug. This makes the `claimed_rewards` undecodeable leading to their stake being stuck. 


This is a referendum whose proposer address (HHJrycDzgkRqQpw5oWUw7iGQMppuNud6LkQdtkxPXhiWQ5i) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

#86 Untitled