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 is a proposal to add SSZ support to builder API in a backward compatible way without requiring to bump the apis to v2.
It outlines what is expected from the client and how a well-behaved server should handle different content types, headers, and use appropriate error codes to allow the client to handle the error.
Notable changes are
submitBlindedBlock
allows to SSZ encoding for both request and response bodygetHeader
allows SSZ encoding of response bodyEth-Consensus-Version
to responses, only required if response body is SSZ encoded but preferably should be added to all responses eventuallySince we can't know if a builder implemented the changes as per spec, the client can determine if SSZ is supported by requesting an SSZ encoded response in the
getHeader
request. Preferably this should be done setting aAccept
header with multiple entries and quality values likeAccept: application/octet-stream;q=1.0,application/json;q=0.9
to give the builder the option to send a JSON response.Related to #53 and #54