fix: set Eth-Execution-Payload-Blinded header on envelope publish - #124
Merged
Conversation
Buildoor always publishes full execution payload envelope contents (never a blinded/payload_root body) to POST /eth/v1/beacon/execution_payload_envelopes, but did not send the Eth-Execution-Payload-Blinded header. Per beacon-APIs #580 the request body is selected by this header; lenient CLs (Lighthouse, Lodestar) infer it from the JSON body, but strict ones (Prysm) reject a missing header with 400, so our reveals fail against Prysm-backed nodes. Set the header statically to "false" since we only ever send full contents.
pk910
approved these changes
Jul 2, 2026
pk910
enabled auto-merge
July 2, 2026 16:12
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.
Problem
When publishing an execution payload envelope to the beacon node, Buildoor POSTs to
/eth/v1/beacon/execution_payload_envelopes(pkg/rpc/beacon/api.go) withContent-Type: application/jsonandEth-Consensus-Version: gloas, but omits theEth-Execution-Payload-Blindedheader.Per beacon-APIs #580, the request body on this endpoint is selected by the
Eth-Execution-Payload-Blindedheader:false→SignedExecutionPayloadEnvelopeContents(full envelope + blobs + KZG proofs)true→SignedBlindedExecutionPayloadEnvelope(BN reconstructs from cache)Lenient CLs (Lighthouse, Lodestar) infer the flow from the JSON body shape and accept the request. But strict CLs — notably Prysm (
PublishExecutionPayloadEnvelopein prysm#16818) — hard-reject a missing header with400 "Eth-Execution-Payload-Blinded header is required". That means Buildoor's reveals fail against any Prysm-backed node on Gloas devnets.Fix
Buildoor always publishes full contents (it never sends a blinded/
payload_rootbody), so the value is staticallyfalse. Set the header explicitly.This covers both publish callers, which share the single
SubmitExecutionPayloadEnvelopemethod:pkg/builderapi/server.go(Builder API reveal)pkg/epbs/reveal_handler.go(ePBS reveal)Notes