-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slashing Period -> Tombstone #2363
Comments
I think this would simplify the logic alot, so I'm very much in favor of it. @cwgoes also suggested the name "exiling" for this. I think thats both more accurate, and a better name for this! |
This will be closed once #3225 is merged |
rather than commenting here would have been more beneficial to add "closes #2363" to the description comment of that PR (you can edit others PR description main comments) ... doing that now |
It's possible that we may be able to remove the concept of slashing period if we introduce the concept of "killing" a validator if it performs a serious malicious act such as a double sign. Under this situation the validator could be pushed out of the validator set with no opportunity of coming back and forcing all the delegations out.
This should be considered post-launch, however as per conversations we may we to do prelaunch if we decided to switch from active slashing (after being informed from #2362)
The text was updated successfully, but these errors were encountered: