double eth1data params #2093
Merged
double eth1data params #2093
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
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.
Ensure the cycle of eth1data voting (follow distance + voting period) is more than a sleep cycle (~8 hours) to more easily allow for intervention/recovery in the event of an issue (attacker or bug).
Rational on the UX degradation: The time it takes to go from eth1 deposit to being inducted as a validator is already perceptibly long to the user and must be due to the security requirements. Doubling this time does not alter the UX much in the grand scheme of things, but provides a much better security profile.
Also, it is worth noting that the expected time to be inducted as a validator is still very small in comparison to the expected validation time for Phase 0 validators (1+ year).
cc: @vbuterin