Beacon slash header validation and fork-gated duplicate evidence#5041
Open
GheisMohammadi wants to merge 1 commit into
Open
Beacon slash header validation and fork-gated duplicate evidence#5041GheisMohammadi wants to merge 1 commit into
GheisMohammadi wants to merge 1 commit into
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.
This PR tightens how beacon blocks carry slashing payloads in the header and how those payloads are validated during state transition. Header slash data is decoded once at the start of block processing. The validation is wired into the shared block processing path so every route that executes a block—including paths that reuse a cached processing result—runs the same checks in the same order. That avoids divergent behavior between full execution and cached replay.
The block proposer path that collects verified slash candidates for the next header was also corrected so that duplicate entries keyed only by evidence identity are not treated as separate successful candidates after they have already been classified as failures.