Support SSZ request body for POST /eth/v2/validator/aggregate_and_proofs - #17318
Open
syjn99 wants to merge 2 commits into
Open
Support SSZ request body for POST /eth/v2/validator/aggregate_and_proofs#17318syjn99 wants to merge 2 commits into
POST /eth/v2/validator/aggregate_and_proofs#17318syjn99 wants to merge 2 commits into
Conversation
Contributor
|
will prysm use of this be added later? |
james-prysm
approved these changes
Aug 13, 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.
What type of PR is this?
What does this PR do? Why is it needed?
https://github.com/ethereum/beacon-APIs/blob/4b4d89a20254d05e2b94c75c8cfd5170ccb77a36/apis/validator/aggregate_and_proofs.v2.yaml#L27-L29
As per
beacon-APIsspec, acceptapplication/octet-streamcontent type (= SSZ encoded) and decode SSZList. This PR doesn't change our VC side: Prysm VC still sends JSON-encodedAggregateAndProofmessage.This PR also includes a helper function using
fastssz'sDecodeDynamicLengthandUnmarshalDynamicwhich are already used in our generated*.ssz.gofiles. First 4 bytes of SSZ List indicates the offset, so it needs to read that part first and it keeps unmarshalling (dynamically) until the byteslice ends.Which issue(s) does this PR fix?
N/A
Other notes for review
Acknowledgements