-
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
Malfeasance2 fetcher and sync #6652
Open
fasmat
wants to merge
28
commits into
develop
Choose a base branch
from
malfeasance-fetcher
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+2,207
−847
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
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 49551 49970 +419
=========================================
+ Hits 39562 39889 +327
- Misses 7742 7811 +69
- Partials 2247 2270 +23 ☔ View full report in Codecov by Sentry. |
bors try |
tryBuild failed: |
fasmat
force-pushed
the
malfeasance-fetcher
branch
from
January 25, 2025 01:58
399733f
to
06d9865
Compare
bors try |
tryBuild failed: |
fasmat
requested review from
dshulyak,
poszu,
ivan4th,
jellonek and
kacpersaw
as code owners
January 25, 2025 02:31
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.
Motivation
This adds the necessary fetcher code for malfeasance v2 so that the node can sync new malfeasance proofs.
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