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.
merkledb
-- rewrite and test range proof invariants; fix proof generation/veriifcation bugs #1629New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merkledb
-- rewrite and test range proof invariants; fix proof generation/veriifcation bugs #1629Changes from all commits
42ad6b6
fbfcac5
675b54e
8146839
5cb9092
4f4bf1f
0b08de4
60729be
4e1518e
5efda97
158e5c3
0ebe0da
babd9a6
622199a
80e67d0
fa67360
5cf991b
091f282
fae5fad
d5054d1
63f1944
106c1b2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems pretty suspicious... Should
start
andend
beMaybe
types being passed into this function?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done in #1657
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved from below since it makes more sense to be here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rewritten to make the invariants more clear
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit to use camelCase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now uses a
Maybe
to properly handle the case where we're verifying a proof that contains only the root. Namely, suppose that we had a range proof for range[nil, [0]]
where the only key-value pair in the proof is for the root, but the database resulting in the proof has more key-value pairs. InRangeProof.Verify
we setlargestPath
to the empty path and calledaddPathInfo
withstartPath
andendPath
both the empty root. This causeshasLowerBound
andhasUpperBound
inaddPathInfo
to befalse
, and we did not add children greater than the root (the empty path), resulting in proof verification failing.In other words, we need to use a
Maybe
to disambiguate between the case where the largest key in the proof is at the root and the case where we shouldn't add any proof node children on the "right" side.