updated private key backup caution message #285
Conversation
✅ Deploy Preview for obol-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -63,7 +63,7 @@ You should expect to see a console output like | |||
| If instead of being shown your `enr` you see an error saying `permission denied` then you may need to [update docker permissions](/docs/int/faq/errors#docker-permission-denied-error) to allow the command to run successfully. | |||
|
|
|||
| :::caution | |||
| Please make sure to create a backup of the private key at `.charon/charon-enr-private-key`. Be careful not to commit it to git! **If you lose this file you won't be able to take part in the DKG ceremony and start the DV cluster successfully.** | |||
| Ensure you create a backup of the private key stored in the '.charon' folder, specifically at '.charon/charon-enr-private-key'. This is the file used to generate your private key. Be careful not to commit it to git! **If you lose this file you won't be able to take part in the DKG ceremony and start the DV cluster successfully.** | |||
There was a problem hiding this comment.
This is the file used to generate your private key
We should clarify that this file doesn't generate the DV private key, but contains the cluster identity key.
There was a problem hiding this comment.
We should also add that they should save the private key as it is used to generate the ENR. Just saving the ENR is useless which is what some operators have been doing as it displays a warning in the CLI to save it. @gsora we should maybe also clarify the CLI?
There was a problem hiding this comment.
We should also add that they should save the private key as it is used to generate the ENR.
💯
we should maybe also clarify the CLI?
When you create an ENR with charon create enr we already print a pretty sizable caution message.
Do you think we should change something with it?
|
Kudos, SonarCloud Quality Gate passed!
|
Summary
Updated the private key backup caution box, so that the text is more clear on what exactly should be backed up
ticket:
#283