fix: validate merkletree using StandardMerkleTree format #244
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
StandardMerkleTree format from official @OpenZeppelin@merkle-tree should be build using keccak hash of keccak hash of leaf data, instead of just keccak hash of leaf data as we do now. This change makes it compatible with that library client side. References: - https://github.com/OpenZeppelin/merkle-tree#validating-a-proof-in-solidity - https://github.com/OpenZeppelin/merkle-tree#standard-merkle-trees > The leaves are double-hashed1 to prevent second preimage attacks.
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.
StandardMerkleTree format from official
@openzeppelin/merkle-treeshould be build using keccak hash of keccak hash of leaf data, instead of just keccak hash of leaf data as we do now.This change makes it compatible with that library client side.
References: