post-gloas payload_attributes event fields - #638
Open
markolazic01 wants to merge 8 commits into
Open
markolazic01 wants to merge 8 commits into
markolazic01 wants to merge 8 commits into
Conversation
This was referenced Aug 31, 2026
Open
Open
Open
Open
krisoshea-eth
added a commit
to krisoshea-eth/lodestar
that referenced
this pull request
Sep 16, 2026
…vents Post-gloas the builder issues its own forkchoiceUpdated to start a payload build, so it needs the safe and finalized execution block hashes the beacon node would use, not only the head. Emit them as optional top-level `safe_block_hash` and `finalized_block_hash` fields next to the standard `payload_attributes` event shape, taken from the same forkchoice lookups the beacon node uses for its own forkchoiceUpdated, and parse them back on the client when present. The fields stay out of the SSZ container so events from beacon nodes that do not send them keep parsing, and they are omitted pre-gloas so the standard shape is unchanged. This replaces the earlier required container fields on this branch. Spec-side discussion: ethereum/beacon-APIs#638.
Contributor
Author
|
Merged to resolve a conflict |
This branch has not been deployed
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.
Description
Introduces
safe_block_hashandfinalized_block_hashtopayload_attributes, from Gloas onwards.Rationale
This event exists so an external process can call
engine_forkchoiceUpdated, but that call requires a fullForkchoiceStateV1(headBlockHash,safeBlockHash,finalizedBlockHash) and the event currently only provides the head,parent_block_hash, which maps toheadBlockHash.The safe and finalized execution hashes therefore complete the
ForkchoiceStateV1object that an external builder passes toengine_forkchoiceUpdated. The builder is a secondforkchoiceUpdatedwriter on the same execution client as the beacon node; inability to retrieve these fields can result in passing different safe and finalized hashes than the node, which would make the execution client's view flip between the two callers.