feat(fuzz): add Merkle trie and MMR fuzz target#825
Open
wangzishuai1987 wants to merge 1 commit into
Open
Conversation
Add fuzz_merkle_trie target that feeds random KV pairs into merkle_root() and MMR append/root operations. Verifies that arbitrary input never causes a panic. Refs: jarchain#229
Contributor
Genesis ReviewComparison targets:
How to reviewPost a comment with the following format (rank from best to worst): Use the short commit hashes above and To meta-review another reviewer's comment, react with 👍 or 👎. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds a
fuzz_merkle_triefuzz target that feeds random key-value pairs into:merkle_root()— binary Patricia Merkle trie root computationappend()+root()— Merkle Mountain Range operationsVerifies that arbitrary input never causes a panic. Keys are deduplicated before passing to the trie (as required by the spec).
This expands fuzz coverage beyond codec/PVM types to the Merklization layer, catching potential issues in:
Refs: #229 (fuzzing infrastructure — "random network message bytes → handler doesn't panic")