Skip to content

Commit

Permalink
update dg slashing wording
Browse files Browse the repository at this point in the history
  • Loading branch information
mehdi-aouadi committed Dec 21, 2023
1 parent 95e2704 commit dfc8737
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/how-to/enable-doppelganger-detection.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Doppelganger detection checks if the validators' keys are already active before

When enabled, doppelganger detection is triggered from two entry points:

1. At [validator client startup](../get-started/start-teku.md#start-teku): If at least one doppelganger is detected, the validator client shuts down after it finishes the check with exit code `2` and should not be restarted by default because more slashing are likely to happen.
1. At [validator client startup](../get-started/start-teku.md#start-teku): If at least one doppelganger is detected, the validator client shuts down after it finishes the check with exit code `2` and should not be restarted by default because slashing are likely to happen.
2. When importing keys via the [key manager API](https://ethereum.github.io/keymanager-APIs/): Any detected doppelganger's keys are ignored (not imported). The other keys are imported and the validators start performing their duties after it finishes the check.

:::warning
Expand Down

0 comments on commit dfc8737

Please sign in to comment.