Repository navigation
Add SSZ list types for gloas API request bodies - #33
Merged
Merged
Conversation
OisinKyne
approved these changes
Sep 30, 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.
Adds generated SSZ list types for the two gloas API request bodies that are bare lists on the wire, mirroring
api/v1.Blobs:apiv1gloas.PayloadAttestationMessages—List[PayloadAttestationMessage, PTC_SIZE](POST /eth/v1/beacon/pool/payload_attestations)apiv1gloas.SignedProposerPreferencesList—List[SignedProposerPreferences, (MIN_SEED_LOOKAHEAD + 1) * SLOTS_PER_EPOCH](POST /eth/v1/validator/proposer_preferences)Both are registered in
api/v1/gloas/generate.yaml, so dynssz-gen emits theMarshalSSZ/UnmarshalSSZimplementations (alignment and list-limit checks included). Thehttpclient's privateproposerPreferencesListand its hand-written marshal loop are replaced by the exported type, so a beacon node built on this library (charon) decodes these bodies with the same generated code the client uses to encode them.Note: the generated list types have pointer receivers, so
SubmitProposerPreferencespasses the list by pointer tomarshalRequestBody. This is only exercised by thehttptests in live mode (HTTP_ADDRESSset), which the fork's CI currently does not run; verified locally against the Platåberget beacon node.