Repository navigation
Fuzzer Protocol v1 extension: add feature-bundle-refinement for RefineBundle to WorkReport fuzzing - #50
Merged
Conversation
sourabhniyogi
changed the title
sourabhniyogi
commented
Sep 1, 2025
|
|
||
| U8 ::= INTEGER (0..255) | ||
| U32 ::= INTEGER (0..4294967295) | ||
| CoreIndex ::= INTEGER (0..65535) |
Contributor
Author
There was a problem hiding this comment.
Decision required concerning whether CoreIndex and Timeslot should be included in the RefineBundle. For simplicity, we could assume that any bundles are processed on core 0, e.g. here
At present, I kept it out, so that the fuzzer target does not have to identify itself as being part of any core, and should accept any work package bundle. In a network setting, this is not the the case.
davxy
approved these changes
Sep 2, 2025
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
2 participants
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 extends the v1 fuzzer protocol to support refinement in a way that is a major stepping stone towards JAM-NP guaranteeing with CE134 use of work package bundles
https://github.com/zdave-parity/jam-np/blob/main/simple.md#ce-134-work-package-sharing
Work package bundles with refinement context may be sent after SetState calls by the fuzzer, and the fuzzer target must return with a Work Report.