-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Unjustifiable reserved amount. Bug? #4160
Comments
@kianenigma Looks like maybe the after effect of a migration or change to deposit config? |
yeah #2562, and more specifically #2562 (comment) |
@shawntabrizi Was the extrinsic to release incorrectly reserved amounts through governance added to any of the recent runtime upgrades? To remind you, we were discussing this in Element for the similar issue with the If it has, then this would be a solution for these accounts too, right? |
A follow up on my comment here. Using this script, I found all the accounts that submitted
Note that there is only one (rather well known) account that is somehow not making sense here, because they should have had some reserved balance left for refund, but somehow they don't. This could probably be linked to the known fact/issue that slashing reserved balances can very well exceed the reserved amount of one pallet and eat the reserved amount of another pallet (something that named-reserves will fix). In any case, I personally think the outcome here is sounds, and I will proceed with making a pull request that does the refund. Lastly, the account of example in this issue is already found and taken care of: 14iGCDW2cEphmcXH22RhbuQBxjAzPP8UJAX8EQw4p5T2ZwsW |
This account:
https://polkadot.subscan.io/account/14iGCDW2cEphmcXH22RhbuQBxjAzPP8UJAX8EQw4p5T2ZwsW
has a reserved balance of 4.95 DOT which should have been released.
The user voted for Council here:
https://polkadot.subscan.io/extrinsic/3643932-1
and reserved 5 DOT for the vote. Then he removed the votes:
https://polkadot.subscan.io/extrinsic/4767206-1
but only 0.05 DOT was unreserved.
He uses the old pallet (electionPhragmen which is now phragmenElections). But the "removeVoter" was also with the old pallet.
The text was updated successfully, but these errors were encountered: