-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: slashed fp inclusion proof (#579)
- Add a new check if the FP was slashed in `ProcessAllPowerDistUpdateEvents` - Func `NewFinalityProviderDistInfo` was also modified to load the properties `IsJailed` and `IsSlashed` from the FP that was in DB (only this check was already enough to fix the issue), but to keep consistency with slashed event processing in the `ProcessAllPowerDistUpdateEvents` the slashed finality provider should not even be included in the `newDc` This check was to avoid activating a slashed FP The slashed FP could be activated if a BTC delegation without inclusion proof was created before the FP was slashed and having the inclusion proof sent after the slashing
- Loading branch information
1 parent
cbcefdc
commit 2df260c
Showing
8 changed files
with
379 additions
and
81 deletions.
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.