-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Allow Removal of Session Key when Offboarded as Validator #8543
Comments
They'd have to prove that they have been out of the validator set for the entire bonding period. The old session keys are needed to verify misbehavior in the "past" and prevent long-range attacks. Once the funds leave the staking system, they should be able to remove the refcount. |
Have This issue been solved? I still can't remove my session key |
@Zeusxs This is not a high priority issue for us since there is a solution i mentioned on the issue:
So you should be able to solve it yourself. I also think we sent you a treasury tip for the funds that were locked right? (so you should come out of this ahead) |
OK, I have not cloudserver to become a validator again at right now, maybe I could propose some treasury tip? right? |
@Zeusxs you dont actually need to a run a validator. Just go through the steps in the UI. A tip is also fine. Link to this chat. |
Thank you very much~, I propose a tip just now, here is my address: 123dYiYNBwu4Wy8FjPuz259e5zhfiFWxdFcPqEm1e8YsAMs8 |
Closed by #10004 |
There is an issue reported here: paritytech/subport#142
Where a user set up their account to be a validator, created a session key, then offboarded as a validator, but still have their Session Key in the system.
Because the session key is in the system, they have a reference counter which does not let them destroy their account.
In order to call
purge_keys
we need to call:This conversion from
AccountId
toValidatorId
is needed because we store the session keys indexed by validator id.The new extrinsic should allow a user to break this lock state by proving the validator doesn't exist in the system and purging their keys because they do not exist.
This should be a "permissionless" call meaning any user can provide this proof.
In this situation, the user facing this issue with cleaning up their account could provide that proof on their own old validator account and clean up their situation without needing to onboard as a validator again.
The text was updated successfully, but these errors were encountered: