[BIT-573] Improve validator epoch and responsives handling#901
Merged
[BIT-573] Improve validator epoch and responsives handling#901
Conversation
Normal epoch duration is blocks_per_epoch if all UIDs have been queried. Try to query each UID at least once - assumes nucleus samples without replacement, but keep maximum epoch duration at 2 * blocks_per_epoch. Typically a low resource validator can complete full network querying in ~350 blocks, so 2 * blocks_per_epoch should normally suffice.
opentaco
requested review from
Eugene-hu,
isabella618033,
shibshib and
unconst
Eugene-hu
approved these changes
Sep 4, 2022
This file contains hidden or 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
2 participants
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.
BIT-573 Improve validator epoch and responsives handling
Adds extra epoch condition to constrain maximum duration.
Removes extra responsive_uids insertion.