Utilize New UpdateRegistry Function #1710
Merged
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
terencechain
approved these changes
Feb 25, 2019
Codecov Report
@@ Coverage Diff @@
## master #1710 +/- ##
==========================================
- Coverage 72.15% 72.08% -0.08%
==========================================
Files 101 100 -1
Lines 7104 7103 -1
==========================================
- Hits 5126 5120 -6
- Misses 1511 1515 +4
- Partials 467 468 +1 |
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.
This is part of #1565
Description
Write why you are making the changes in this pull request
We were not using the UpdateRegistry function anywhere in our code as needed by the spec. Additionally, ValidatorRegistryUpdateEpoch was set to far future slot instead of the genesis slot.