-
Notifications
You must be signed in to change notification settings - Fork 696
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
Beefy equivocation: check all the MMR roots #5857
Merged
serban300
merged 6 commits into
paritytech:master
from
serban300:beefy-equivocation-runtime
Oct 1, 2024
Merged
Beefy equivocation: check all the MMR roots #5857
serban300
merged 6 commits into
paritytech:master
from
serban300:beefy-equivocation-runtime
Oct 1, 2024
Conversation
This file contains 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
serban300
added
R0-silent
Changes should not be mentioned in any release notes
T15-bridges
This PR/Issue is related to bridges.
labels
Sep 27, 2024
Normally, the BEEFY protocol only accepts a single MMR Root entry in a commitment's payload. But to be extra careful, when validating equivocation reports, let's check all the MMR roots, if there are more.
serban300
force-pushed
the
beefy-equivocation-runtime
branch
from
September 27, 2024 11:19
b9390bf
to
e7687d6
Compare
bkchr
approved these changes
Sep 27, 2024
acatangiu
approved these changes
Sep 30, 2024
acatangiu
removed
the
R0-silent
Changes should not be mentioned in any release notes
label
Sep 30, 2024
needs prdoc and is good to go |
acatangiu
requested changes
Oct 1, 2024
acatangiu
approved these changes
Oct 1, 2024
paritytech-ci
pushed a commit
that referenced
this pull request
Oct 1, 2024
Normally, the BEEFY protocol only accepts a single MMR Root entry in a commitment's payload. But to be extra careful, when validating equivocation reports, let's check all the MMR roots, if there are more. --------- Co-authored-by: Adrian Catangiu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Normally, the BEEFY protocol only accepts a single MMR Root entry in a commitment's payload. But to be extra careful, when validating equivocation reports, let's check all the MMR roots, if there are more.