Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Untitled Post
3 years ago
Executed
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.
Comments (3)
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (328)0.0 DOT
Support0.0 DOT
Nay (8)0.0 DOT
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:
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 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.