### Path to fast-unstake on Kusama

- Original PR:[ https://github.com/paritytech/substrate/pull/12129]( https://github.com/paritytech/substrate/pull/12129) 
- Section in Polkadot Staking Update: [Staking Update: August-September 2022](https://polkadot.network/blog/staking-update-august-september-2022/#fast-unstake)

this feature is there to allow those that have staked by mistake, or for whatever reason, are no longer actually exposed (and are thus not earning any rewards anymore – exactly like a recent report here: [Only inactive validators after nomination - #3 by kianenigma) to unstake faster.](https://forum.polkadot.network/t/only-inactive-validators-after-nomination/1515/3)

This pallet already exists in all runtimes. The pallet works of the basis of using leftover block weights, and using it optionally (`on_idle`, for the technical folks) to progress the unstake process. The pallet consumes only a maximum amount of weight, measured in the number of eras that are checked per block (`ErasToCheckPerBlock`).

This cap is currently set to 0 in Polkadot and Kusama, and thus the pallet is effectively not doing anything. On westend, the pallet has been enabled for a while now, and has been tested. 

The most note-worthy issues is that an unexposed nominator who also happened to have been slashed in the past cannot use this pallet. First, this is a very rare case anyhow, because to be slashed, one needs to have been exposed at some point, which contradicts the main requirement of fast-unstake: it is only for unexposed nominators. So, only a small group of nominators will be applicable to this. Moreover, any UI can easily detect this situation and not recommend that fast-unstake process to the nominator if they have been slashed in the past.

The second issues that we have found so far is that the while the fast-unstake process does not take too much weight under any circumstance, it might mistakenly report a very large amount of weight for itself. This might have the consequence of next `on_idle` hooks in the runtime being starved, but it has no serious consequence on the rest of the system. Moreover, no pallets other than fast-unstake in Polkadot and Kusama runtime are using `on_idle.`

Both issues are fixed. 

The call needed to enable the feature are as follows: Kusama -[ Polkadot/Substrate Portal](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.dwellir.com#/extrinsics/decode/0x2a0201000000). 

This proposal should enable fast-unstake in Kusama, as explained [here](https://forum.polkadot.network/t/path-to-fast-unstake-in-polkadot-kusama/1539).

call

Executed

Submitted

DecisionStarted

DecisionDepositPlaced

ConfirmStarted

Confirmed

whitelisted_caller

Enable conditional fast-unstake service in Kusama

candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

root

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

big_spender

Origin for signaling that the network wishes for some change

Able to spend up to 333,333.3333 KSM from the treasury at once

Managing the composition of the fellowship

Able to spend up to 8.3333 KSM from the treasury at once

Able to spend up to 33.3333 KSM from the treasury at once

Able to spend up to 333.3333 KSM from the treasury at once

Able to spend up to 3,333.3333 KSM from the treasury at once

Able to spend up to 33,333.3333 KSM from the treasury at once