spec: add muxed_decode vectors for edge ids and invalid case - #40
Merged
Conversation
codeZe-us
self-requested a review
February 24, 2026 16:41
codeZe-us
approved these changes
Feb 24, 2026
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
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.
This pull request expands the test coverage in
spec/vectors.jsonby adding new test cases for muxed address decoding, especially covering edge cases and boundary values, and improves the formatting for readability. The most significant changes are grouped below:New muxed address decode test cases
Improved formatting for test vectors
tagsarrays to multi-line for consistency and readability across the file. [1] [2] [3] [4] [5] [6] [7]Closes Add muxed_decode vectors to spec/vectors.json #36