Add parent_block_root to bid filtering key - #5001
Merged
Merged
Conversation
Previously, the highest-value bid was tracked per `(slot, parent_block_hash)`. This meant that if there were competing beacon chain forks with different `parent_block_roots` but the same execution parent, a high bid on one fork could cause valid bids for another fork to be ignored. By including `parent_block_root` in the tuple, bids are now tracked independently per fork, preventing cross-fork interference.
bharath-123
approved these changes
Mar 12, 2026
jihoonsong
approved these changes
Mar 12, 2026
jtraglia
enabled auto-merge (squash)
March 12, 2026 17:09
nflaig
added a commit
to ChainSafe/lodestar
that referenced
this pull request
Apr 6, 2026
Update to match ethereum/consensus-specs#5001 wording. The underlying implementation already keys bids by the (slot, parent_block_root, parent_block_hash) tuple.
tersec
pushed a commit
to status-im/nimbus-eth2
that referenced
this pull request
May 25, 2026
The gossip rule was changed from: > [IGNORE] This bid is the highest value bid seen for the corresponding > slot and the given parent block hash to: > [IGNORE] this bid is the highest value bid seen for the tuple > (bid.slot, bid.parent_block_hash, bid.parent_block_root)`. - ethereum/consensus-specs#5001 This way, someone can't just abuse a reorg to bid a large amount on a non-canonical branch to purge the canonical bid. Catch up with spec. Further, clean up the `parentExecHash != bid.parent_block_hash` check which is not from spec and rejected bids building on the timeline where the parent block's payload was withheld, by tracking the bids in the pool separately based on timeline.
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.
Previously, the highest-value bid was tracked per
(slot, parent_block_hash). This meant that if there were competing beacon chain forks with differentparent_block_rootsbut the same execution parent, a high bid on one fork could cause valid bids for another fork to be ignored. By includingparent_block_rootin the tuple, bids are now tracked independently per fork, preventing cross-fork interference.