Fix execution block / receipts JSON downloads on Gloas slots#666
Merged
Fix execution block / receipts JSON downloads on Gloas slots#666
Conversation
…oads The "Execution Block" and "Block Receipts" JSON downloads on the slot details page failed with "block has no execution payload" on every EIP-7732 (Gloas) block, because the versioned beacon block no longer carries the execution payload inline — it lives in the separate signed execution payload envelope. Add a resolveExecutionPayload helper that falls back to blockData.Payload.Message.Payload for Gloas+ blocks, mirroring the pattern already used in handlers/slot.go for the rendered slot view, and route both download handlers through it.
parithosh
approved these changes
Apr 29, 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.
Summary
eth_getBlockByHash) and Block Receipts JSON downloads on the slot details page errored withblock has no execution payloadon every Gloas (EIP-7732) slot.VersionedSignedBeaconBlock.ExecutionPayload()explicitly returns"no execution payload in gloas"because in EIP-7732 the payload moved out of the beacon block body into the separate Signed Execution Payload Envelope. Both download handlers inhandlers/slot_download.goonly consulted the inline payload.resolveExecutionPayloadwhich, forDataVersionGloas/Heze, synthesises a*spec.VersionedExecutionPayloadfromblockData.Payload.Message.Payload— the same pattern already used inhandlers/slot.go:812for the rendered slot view. BothhandleBlockBodyDownloadandhandleReceiptsDownloadnow flow through it; pre-Gloas behaviour is unchanged.Test plan
block has no execution payload.