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: docs/run-node/4-register-validator.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,8 +114,8 @@ Only provide values which differ from the defaults to avoid issues with future u
114
114
It's imperative that prior to staking your node, you backup all three files that identify your node.
115
115
These files will be generated when the node is started for the first time.
116
116
117
-
*`staker.key` and `staker.crt` - Make up your NodeID
118
-
*`signer.key` - Defines your node's proof of possession (NodePOP). It generates the BLS key and BLS signature required for staking.
117
+
-`staker.key` and `staker.crt` - Make up your NodeID
118
+
-`signer.key` - Defines your node's proof of possession (NodePOP). It generates the BLS key and BLS signature required for staking.
119
119
120
120
If these staking keys are lost due to host migrations or disaster scenarios, you will no longer be able to run the node as it's previous identity.
121
121
This poses a risk of staked funds being locked against the unrecoverable NodeID until expiry of that stake, resulting in a loss of rewards and negatively impacting the network.
0 commit comments