Include recently slashed churn in exit churn queue #785
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vbuterin
reviewed
Mar 16, 2019
Closed
djrtwo
reviewed
Mar 19, 2019
specs/core/0_beacon-chain.md
Outdated
| balance_churn += get_effective_balance(state, index) | ||
| if balance_churn > max_balance_churn: | ||
| break | ||
| if state.current_epoch < state.validator_registry_update_epoch + LATEST_SLASHED_EXIT_LENGTH: |
There was a problem hiding this comment.
Why are you blocking exits if there have been LATEST_SLASHED_EXIT_LENGTH epochs since last registry update?
There was a problem hiding this comment.
See discussing here. It's a simplification to avoid caching a slashed_balance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #527 in combination with #784.
These changes were made to keep a tighter bound on validator churn to ensure adequate safety margins when changing v-sets