Edit generate keys page

This commit is contained in:
yslcrypto 2020-12-07 11:01:48 +01:00
parent 34eb5d33c8
commit e73f3e77b8
1 changed files with 4 additions and 4 deletions

View File

@ -6,7 +6,7 @@ Every time you generate a keystore from your mnemomic, that keystore is assigned
To stay consistent with the rest of the book, we'll take you though how to do this using the [deposit-cli's](https://github.com/ethereum/eth2.0-deposit-cli) [binary executable](https://github.com/ethereum/eth2.0-deposit-cli/releases).
Specifically, we'll be using the `existing-mnemonic` command. According to the deposit-cli's [README](https://github.com/ethereum/eth2.0-deposit-cli#step-2-create-keys-and-deposit_data-json):
Specifically, we'll be using the `existing-mnemonic` command. Here's a description of the command from the deposit-cli's [README](https://github.com/ethereum/eth2.0-deposit-cli#step-2-create-keys-and-deposit_data-json):
> This command is used to re-generate or derive new keys from your existing mnemonic. Use this command, if (i) you have already generated keys with this CLI before, (ii) you want to reuse your mnemonic that you know is secure that you generated elsewhere (reusing your eth1 mnemonic .etc), or (iii) you lost your keystores and need to recover your keys.
@ -36,12 +36,12 @@ Copy the `validator_keys` directory to `nimbus-eth2` and then follow the instruc
## Generate another key
***N.B.** the commands below assume you already have one key and wish to generate a second, hence `--validator_start_index` has been set to `0`.*
> ⚠️ If you wish to generate another validator key, you must take great care
to not generate a copy of your original key. Running the same key on two different validator clients will likely get you slashed.
***N.B.** the commands below assume you already have one key and wish to generate a second, hence `--validator_start_index` has been set to `0`.*
Run the following command from the directory which contains the `deposit` executable:
**Pyrmont**