feat: impl merkle_proof spec test #80
Draft
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
Signed-off-by: grapebaba <[email protected]>
Contributor
Author
|
@twoeths I draft a init implementation for merkle_proof spec test. The one thing I found it is missing proof API in ssz-z like ssz-ts, currently I simply put it in the test code, is there any issue already there to track this? |
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.
Motivation
Support merkle_proof spec tests follow the consensus-spec-tests.
Description
merkle_proofrunner and writer follow the current design .merkle_proofrunner: registers the handler, ensures output directories exist, iterates nested suite/case folders, and emits generated cases via the new writer module.