Use head_state for epoch boundary root note#4881
Merged
jtraglia merged 1 commit intoJan 30, 2026
Merged
Conversation
head_state for epoch boundary root notehead_state for epoch boundary root note
jtraglia
approved these changes
Jan 30, 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
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.
The FFG section in the honest validator spec described looking up
epoch_boundary_block_rootwithget_block_root(state, get_current_epoch(head_state))while all preceding steps consistently usehead_state.Although this does not change the computed value, the mixed naming is confusing for implementers and suggests the wrong state object is being referenced.