Verify beacon header slash records during block processing#5068
Merged
Conversation
mur-me
approved these changes
Jun 26, 2026
|
Tick the box to add this pull request to the merge queue (same as
|
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
2 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.
Beacon chain blocks can carry slash records in the block header. Those records are already validated when they enter the pending-slash queue and when a block proposer collects slashes for inclusion, but the block processing path did not run the same validation before applying them during finalization.
This PR adds that validation in
StateProcessor.Processfor beacon chain blocks. Each decoded header slash record is checked with the existing slash.Verify logic before finalization proceeds, so block import and local execution follow the same rules as the rest of the slash pipeline.