Skip to content
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

Closed
rigelrozanski opened this issue Sep 20, 2018 · 4 comments

Comments

Projects
None yet
5 participants
@rigelrozanski
Copy link
Member

commented Sep 20, 2018

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)

@ValarDragon

This comment has been minimized.

Copy link
Member

commented Oct 21, 2018

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!

@rigelrozanski

This comment has been minimized.

Copy link
Member Author

commented Oct 22, 2018

This is where validators go when they've been bad
s12_panama_exile_island_cu

@jackzampolin

This comment has been minimized.

Copy link
Contributor

commented Jan 9, 2019

This will be closed once #3225 is merged

@rigelrozanski

This comment has been minimized.

Copy link
Member Author

commented Jan 10, 2019

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

@sunnya97 sunnya97 referenced this issue Jan 10, 2019

Merged

R4R: Tombstone Implementation #3225

4 of 5 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.