fix: add merkle path verification #43
Merged
Conversation
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
d70-t
reviewed
Dec 11, 2025
Collaborator
d70-t
left a comment
d70-t
left a comment
There was a problem hiding this comment.
Thanks a lot, for fixing this long outstanding issue. The change mostly seems fine, but there seems to be a typo in the car file name.
Co-authored-by: Tobias Kölling <tobi@die70.de>
Closed
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.
What
Verify the merkle proof from the root CID (passed in the input) to the resolved block (the terminal element which is typically a file or folder), e.g.
{CID]/mydir/myfile.jpgto ensure that the data is verified.Why
This ensures that data is fetched trustlessly without trusting the gateway to return the correct data.
This is a follow-up to #40 as noted in #39 (comment)