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

Churn queue bypass #802

Closed
JustinDrake opened this issue Mar 18, 2019 · 2 comments
Closed

Churn queue bypass #802

JustinDrake opened this issue Mar 18, 2019 · 2 comments
Labels
general:enhancement New feature or request

Comments

@JustinDrake
Copy link
Collaborator

A rational validator may bypass the churn queue by voluntarily slashing himself if he's in a hurry to get his money. Because of partial slashing the validator only loses 1/32nd of its balance at stake in the best case.

Should we replace exit_validator by initiate_validator_exit in slash_validator to avoid this queue bypass? This would also be a cleaner way of handling #785 and would simplify the validator state machine since all exits (voluntary exits, ejections, slashings) would go through the same exit pipeline stages.

@JustinDrake JustinDrake added the general:enhancement New feature or request label Mar 18, 2019
@vbuterin
Copy link
Contributor

That's what the longer 36-day time-to-exit if you get slashed is meant to discourage. I would say when we do the validator queue -> exit queue reform, set that time to exit to be equal to the time needed to go through the queue if you were behind every currently bonded validator.

@JustinDrake
Copy link
Collaborator Author

This is addressed in the exit/withdrawal queue refactor #850

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
general:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants