forked from ChainSafe/lodestar
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: integrate gossip validation spec tests (consensus-specs #4902) #3
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
199c2ab
feat: integrate gossip validation spec tests (73/74 passing)
lodekeeper 5356ebc
Merge remote-tracking branch 'fork/unstable' into feat/gossip-validat…
lodekeeper 58a0cf5
chore: address review feedback on gossip test PR
lodekeeper 85f8ab5
test: remove section heading comments in networking spec test
lodekeeper 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
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.
aren't we validation that somewhere else already, can you please check and share which gossip rule this is with a reference to the spec
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.
Checked — this specific condition is not covered by . That helper validates slashable attestation data + indexed attestation validity/signatures, but it does not enforce that any intersecting validator is currently slashable.\n\nSpec reference: gossip requires all conditions to pass, and in we must end with after iterating intersecting indices. This check enforces that precondition on gossip path. I also added an inline code comment clarifying this.
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.
Follow-up with exact refs (my previous comment dropped some formatting): this is from the gossip attester slashing validation flow in
p2p-interface.md(validate_attester_slashing). After validating both indexed attestations, the rule requires finding at least one overlapping validator index whereis_slashable_validator(...)is true; otherwise the object must be ignored/rejected by gossip validation.assertValidAttesterSlashingdoes not enforce that intersection+slashable condition, so this check is needed on the gossip path.