-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Merged by Bors] - Malfeasance2 fetcher and sync #6652
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## develop #6652 +/- ##
=========================================
- Coverage 79.8% 79.8% -0.1%
=========================================
Files 366 366
Lines 49517 49967 +450
=========================================
+ Hits 39564 39886 +322
- Misses 7711 7811 +100
- Partials 2242 2270 +28 ☔ View full report in Codecov by Sentry. |
bors try |
tryBuild failed: |
399733f
to
06d9865
Compare
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
bors merge |
## Motivation This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs.
Build failed: |
bors merge |
## Motivation This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs.
Build failed: |
flaky unit test on windows bors merge |
## Motivation This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs.
Build failed: |
bors merge |
## Motivation This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs. Closes #6689
Pull request successfully merged into develop. Build succeeded: |
Motivation
This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs.
Closes #6689
Description
Initially legacy malfeasance proofs will continue to be managed and synced as before and malfeasance v2 proofs work independently of them. Which means everywhere in the codebase where we check for malicious identities we need to check for both
identities.IsMalicious
(v1) andmalfeasance.IsMalicious
(v2). Legacy malfeasance proofs will be migrated to v2 at a later point together with deprecating the legacy malfeasance protocol.Test Plan
TODO