-
Notifications
You must be signed in to change notification settings - Fork 478
[Feature] Support for Merkle exclusion proofs #1116
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
Merged
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
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.
Some minor formatting nits, but once those are addressed, this is good to go.
iamalwaysuncomfortable
approved these changes
Oct 29, 2025
Signed-off-by: Roy Rotstein <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Motivation
Wallets built on the SDK will that will support compliant stablecoins will need to generate a Merkle exclusion proof in order to prove non-inclusion on a freeze list. Given a Merkle tree in the form of a vector of Aleo field elements, the support code in this PR will be able to generate a Merkle path based on a user's address. The address will be converted to a field element. The leaves of the Merkle tree are sorted. Two Merkle paths are generated at the indices where the address would be inserted if that address were part of the Merkle tree.
Test Plan
The test directory includes a test file containing tests for the happy path and fail cases.