Defer payload processing to next block#5094
Merged
jtraglia merged 60 commits intoethereum:masterfrom Apr 16, 2026
Merged
Conversation
potuz
reviewed
Apr 10, 2026
twoeths
reviewed
Apr 10, 2026
tbenr
reviewed
Apr 10, 2026
twoeths
reviewed
Apr 10, 2026
jtraglia
reviewed
Apr 10, 2026
jtraglia
reviewed
Apr 10, 2026
jtraglia
reviewed
Apr 10, 2026
ensi321
reviewed
Apr 11, 2026
bharath-123
reviewed
Apr 11, 2026
kevaundray
reviewed
Apr 11, 2026
potuz
reviewed
Apr 16, 2026
jtraglia
approved these changes
Apr 16, 2026
jihoonsong
reviewed
Apr 16, 2026
Member
|
All, this PR has grown quite large (~100 comments & 60 commits). It's clear to me that (1) we agree that this is appropriate strategy and (2) it's in a good enough state to be merged. I'm sure there are little tweaks we can make, but let's merge this and follow up with smaller, more targeted PRs. Great work everyone! |
potuz
added a commit
to potuz/EIPs
that referenced
this pull request
Apr 17, 2026
Nico has done extensive study of the EIP and merged ethereum/consensus-specs#5094 which is a considerable contribution.
This was referenced Apr 19, 2026
ericsson49
added a commit
to ericsson49/eth2.0-specs
that referenced
this pull request
Apr 20, 2026
ericsson49
added a commit
to ericsson49/eth2.0-specs
that referenced
this pull request
Apr 20, 2026
jtraglia
pushed a commit
that referenced
this pull request
Apr 20, 2026
jtraglia
pushed a commit
that referenced
this pull request
Apr 20, 2026
From the discussion with Lido on discord [here](https://discord.com/channels/595666850260713488/1494024415896408154) it would be helpful for them (and other protocols) to clarify how to get consistent state on CL + EL after gloas. Note, this is not something that changed in #5094, the pre-deduction of withdrawals from validator balances before crediting them on the EL side exists already in `alpha.4`.
nflaig
added a commit
to ChainSafe/lodestar
that referenced
this pull request
Apr 21, 2026
…9209) related to changes in ethereum/consensus-specs#5094, we wanna avoid using `is_parent_block_full`
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.
Under the current gloas spec, a single block root can correspond to two different post-states depending on whether the payload has been seen. This breaks several spec invariants that hold on mainnet since phase0
proposer_lookaheadandptc_window) across epoch boundariesstore_target_checkpoint_stateuses the post-block state while fork choice may use the post-payload state, producing divergent epoch transitions and weakening FFG guarantees (@potuz may disagree). This affects justified balances in fork choice weight calculations which is currently underspecified as noted in Fork-choice justified balances in underspecified post-Gloas #5074is_within_weak_subjectivity_periodandcompute_weak_subjectivity_periodoperate on a checkpoint state that is now ambiguous due to the post-block state missing execution request effectsThis PR defers execution payload processing (except verification) to the next beacon block's
state_transitionvia a newprocess_parent_execution_payloadfunction.process_execution_payloadremains as a pure verification step on payload arrival. This eliminates the dual state architecture (block_states/payload_states) introduced in the current gloas spec and restores a single canonical post-state per block root, restoring all three invariants noted above without requiring more invasive changes like updating theCheckpointtype as proposed here as an alternative solution.cc @wemeetagain, @ensi321, @twoeths