-
Notifications
You must be signed in to change notification settings - Fork 75
fix: ignore stale finalized payloads in fork choice #820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tcoratger
merged 3 commits into
leanEthereum:main
from
latifkasuli:fix/ignore-stale-forkchoice-payloads
Jun 4, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is a great anchor for the bug you're fixing — it's exactly the "stale message masks a fresh one" case, so I'd keep it as-is. 👍
To round things out, here's a companion test vector I'd suggest adding right alongside it. It encodes the mirror-image situation from my inline note: a vote whose head is above finalized but whose target sits at the finalized slot. It should still earn weight.
Heads up: on the branch as it stands today this test fails (
compute_block_weightsreturns{}), which is precisely the behavior I was flagging. Once the filter keys onhead.slot, it passes — so it doubles as the regression guard that keeps this from creeping back later. 🙂And if you wanted to take the maintainer's earlier "maybe a test vector?" nudge all the way to cross-client land, both of these (the masking case and this mirror case) would make lovely consensus fillers under
tests/consensus/lstar/fc/, modeled ontest_store_pruning.py— build the finalized chain withBlockStep, drop the aggregates in withGossipAggregatedAttestationStep, then assert the chosen head withStoreChecks. Totally optional, just flagging the path. 🙏