Require the caller of checkLeaderValue to provide bounds.
#2776
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
The input to `checkLeaderValue` is now not guaranteed to be the output of a VRF evaluation. Consequently, we require the input to explicitly specify its bounds. We only provide one way to construct a 'BoundedNatural', which will throw an error if the bound is violated. This is most appropriate for our use case, since we "know" the bounds statically, and a violation indicates a programmer error.
JaredCorduan
approved these changes
May 10, 2022
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.
The input to
checkLeaderValueis now not guaranteed to be the outputof a VRF evaluation. Consequently, we require the input to explicitly
specify its bounds.
We only provide one way to construct a 'BoundedNatural', which will
throw an error if the bound is violated. This is most appropriate for
our use case, since we "know" the bounds statically, and a violation
indicates a programmer error.