-
Notifications
You must be signed in to change notification settings - Fork 589
New 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
imp: cleanup verifcation arg code for 23-commitment #7493
Open
colin-axner
wants to merge
9
commits into
main
Choose a base branch
from
colin/23-commitment-cleanup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
7e0deea
imp: cleanup verifcation arg code for 23-commitment
colin-axner 7a7fa89
Update modules/core/23-commitment/types/merkle.go
colin-axner e61f947
Update modules/core/23-commitment/types/merkle_test.go
colin-axner 37f89a7
chore: review followups
colin-axner 470d7bd
Merge branch 'main' of github.com:cosmos/ibc-go into colin/23-commitm…
colin-axner a43f256
Update modules/core/23-commitment/types/merkle.go
colin-axner c8f845f
Merge branch 'main' of github.com:cosmos/ibc-go into colin/23-commitm…
colin-axner 78f9049
Merge branch 'colin/23-commitment-cleanup' of github.com:cosmos/ibc-g…
colin-axner 9678b56
Merge branch 'main' into colin/23-commitment-cleanup
DimitrisJim File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
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.
Maybe we could indicate in godoc why this is. e.g. key path of length > 1 is expected to be a chained proof.
Every path element inside
path.KeyPath
is expected to have a corresponding proofSpec, right? In the normal case first we calculate subroots for inclusion/non-inclusion and then inclusion of the subroot in commitment root.Only in the case of
path.KeyPath == 1
, would we be able to do a single inclusion or non-inclusion proof.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.
Correct. This code is expecting to receive a list of keys which corresponds to different trees (which is why it must be a list of specs, 1 per tree)