You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: beacon_chain/conf.nim
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,11 @@ type
51
51
enabled ="Always enabled"
52
52
disabled ="Always disabled"
53
53
54
+
GossipSlashingProtectionMode* {.pure.} =enum
55
+
dontcheck
56
+
warn
57
+
stop
58
+
54
59
BeaconNodeConf*=object
55
60
logLevel* {.
56
61
defaultValue: "INFO"
@@ -255,6 +260,12 @@ type
255
260
desc: "Write SSZ dumps of blocks, attestations and states to data dir"
256
261
name: "dump" }: bool
257
262
263
+
gossipSlashingProtection* {.
264
+
defaultValue: GossipSlashingProtectionMode.warn
265
+
desc: "[=warn*|stop] What to do when another validator is detected to be running the same validator keys (default `warn`, will become `stop` in the future)"
266
+
name: "gossip-slashing-protection"
267
+
}: GossipSlashingProtectionMode
268
+
258
269
of createTestnet:
259
270
testnetDepositsFile* {.
260
271
desc: "A LaunchPad deposits file for the genesis state validators"
if self.config.gossipSlashingProtection ==GossipSlashingProtectionMode.stop:
340
+
warn"We believe you are currently running another instance of the same validator. We've disconnected you from the network as this presents a significant slashing risk. Possible next steps are (a) making sure you've disconnected your validator from your old machine before restarting the client; and (b) running the client again with the gossip-slashing-protection option disabled, only if you are absolutely sure this is the only instance of your validator running, and reporting the issue at https://github.com/status-im/nimbus-eth2/issues."
0 commit comments