fix: process timely flags for forks >= Altair #15994
Open
Conversation
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
1 participant
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.
Problem: processIncludedAttestation() gated timely-flag handling by state.Version() == version.Altair, which disables processing on all forks after Altair (Bellatrix, Capella, Deneb, Electra, Fulu). This causes missing timely flag updates and metrics beyond Altair despite participation bits and flag indices existing in later forks.
Fix: Change the gate to state.Version() >= version.Altair so the logic runs on all post-Altair versions.
Tests: Added TestProcessIncludedAttestation_Bellatrix to ensure timely flags are processed in Bellatrix using a deterministic Bellatrix genesis and participation bits; asserts the same “Attestation included” logs and timely flags as the Altair test.