Extend light client protocol for Gloas#5178
Merged
Merged
Conversation
As part of Gloas, the execution data in the beacon block no longer refers to the latest canonical data, but instead just to a potential future payload that may or may not become canonical depending on the PTC attestations. The latest canonical data is available in the state's `latest_block_hash`, mirrored in the block's `parent_block_hash`. As state access is tricky, the `execution_branch` for post-Gloas blocks now is for the `parent_block_hash` in the block's bid. Further, Gloas removes the `ExecutionPayloadHeader` from both the beacon block _and_ state. Therefore, corresponding light client data structures can now only commit to the `block_hash` field. In transition situations where `finalized_header` points to pre-Gloas while `attested_header` is post-Gloas, or in syncing situations where a `LightClientStore` is Gloas but wants to sync pre-Gloas data, existing `LightClientHeader` upgrades dynamically create a new `execution_branch` for the `block_hash` field, discarding the rest of the payload header during the upgrade.
etan-status
added a commit
to status-im/nimbus-eth2
that referenced
this pull request
Apr 28, 2026
Define the types and helpers needed for Gloas light client specs. - ethereum/consensus-specs#5178
wemeetagain
reviewed
Apr 28, 2026
tersec
pushed a commit
to status-im/nimbus-eth2
that referenced
this pull request
Apr 28, 2026
* Add Gloas light client containers Define the types and helpers needed for Gloas light client specs. - ethereum/consensus-specs#5178 * Cleanup indexing * Add spec references * Cleanup upgrade_lc_header_to_gloas * Use static for default * Use correct source for building the proof * More static * Update zero hash comparison
wemeetagain
approved these changes
Apr 28, 2026
Contributor
Author
|
Partially ran it against Nimbus, should be alright now. |
jtraglia
approved these changes
Apr 28, 2026
jtraglia
left a comment
Member
There was a problem hiding this comment.
Awesome. Looks good to me. Nice work @etan-status!
tersec
pushed a commit
to status-im/nimbus-eth2
that referenced
this pull request
Apr 29, 2026
* Add LightClientDataFork.Gloas Introduce Gloas helpers for processing light client data: - ethereum/consensus-specs#5178 * Regen tests md
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
3 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.
As part of Gloas, the execution data in the beacon block no longer refers to the latest canonical data, but instead just to a potential future payload that may or may not become canonical depending on the PTC attestations. The latest canonical data is available in the state's
latest_block_hash, mirrored in the block'sparent_block_hash. As state access is tricky, theexecution_branchfor post-Gloas blocks now is for theparent_block_hashin the block's bid.Further, Gloas removes the
ExecutionPayloadHeaderfrom both the beacon block and state. Therefore, corresponding light client data structures can now only commit to theblock_hashfield. In transition situations wherefinalized_headerpoints to pre-Gloas whileattested_headeris post-Gloas, or in syncing situations where aLightClientStoreis Gloas but wants to sync pre-Gloas data, existingLightClientHeaderupgrades dynamically create a newexecution_branchfor theblock_hashfield, discarding the rest of the payload header during the upgrade.