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
-:test_tube: Run `yarn check-types` to check TypeScript types.
33
33
-:test_tube: Run `yarn lint` to run the linter (ESLint).
34
34
35
-
Note that to run `test:e2e`, first ensure that the environment is correctly setup by running the `run_e2e_env.sh` script.
35
+
Note that to run `test:e2e`, first ensure that the environment is correctly setup by running the `run_e2e_env.sh` script. This script requires a running docker engine.
Copy file name to clipboardexpand all lines: docs/pages/validator-management/vc-configuration.md
+37-39
Original file line number
Diff line number
Diff line change
@@ -4,37 +4,24 @@ The following instructions are for stakers utilizing the Lodestar validator clie
4
4
5
5
[TOC]
6
6
7
-
## Wallet configuration
8
-
9
-
A wallet helps to manage many validators from a group of 12/24 words (also known as a "mnemonic" or "recovery phrase"). All validators and withdrawal keys can be re-generated from a backed-up mnemonic.
10
-
11
-
The mnemonic is randomly generated during wallet creation and printed out to the terminal. It's important to make one or more backups of the mnemonic to ensure your ETH wallets are not lost in the case of data loss.
12
-
13
-
<!-- prettier-ignore-start -->
14
-
!!! danger
15
-
It is very important to keep your mnemonic private as it represents the ultimate control of your ETH wallets.
16
-
<!-- prettier-ignore-end -->
7
+
## Setup your validator
17
8
18
-
### Create a wallet
9
+
Validators are represented by a BLS keypair. Use your generated mnemonic from one of the tools above to generate the keystore files required for validator duties on Ethereum using the Lodestar validator client.
19
10
20
-
Lodestar has removed its functionality to create wallets.
11
+
### Create a keystore
21
12
22
-
To create a wallet, we recommend using the official [`staking-deposit-cli`](https://github.com/ethereum/staking-deposit-cli/releases) from the Ethereum Foundation for users comfortable with command line interfaces.
13
+
To create a keystore, we recommend using the official [Staking Deposit CLI](https://github.com/ethereum/staking-deposit-cli/releases) from the Ethereum Foundation for users comfortable with command line interfaces.
23
14
24
15
Alternatively, for a graphical user interface, you can use the [Stakehouse Wagyu Key Generator](https://wagyu.gg/) developed by members of the EthStaker community.
25
16
26
17
<!-- prettier-ignore-start -->
27
-
!!! info
28
-
These tools will generate files for staking validators as well as the important mnemonic. This mnemonic must be handled and stored securely.
18
+
!!! warning
19
+
These tools will generate keystore files for staking validators as well as the important mnemonic. This mnemonic must be handled and stored securely.
29
20
<!-- prettier-ignore-end -->
30
21
31
-
## Setup your validator
32
-
33
-
Validators are represented by a BLS keypair. Use your generated mnemonic from one of the tools above to generate the keystore files required for validator duties on Lodestar.
22
+
### Import a validator keystore to Lodestar
34
23
35
-
### Import a validator keystore from your wallet to Lodestar
36
-
37
-
To import a validator keystore that was created via one of the methods described above, you must locate the validator JSON keystores exported by those tools (ex. `keystore-m_12381_3600_0_0_0-1654128694.json`).
24
+
To import a validator JSON keystore that was created via one of the methods described above, you must locate the file for import (ex. `keystore-m_12381_3600_0_0_0-1654128694.json`).
38
25
39
26
Inside the keystore JSON file, you should have an [EIP-2335 keystore file](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-2335.md#json-schema).
The interactive passphrase import method will prompt every keystore in the `validator_keys` folder for import and will ask for the individual password for each keystore. **This method will allow you to import multiple keystores with different passwords.**
62
49
63
-
The plaintext passphrase file import method will allow to import all keystores in the `validator_keys` folder with the same password contained in `password.txt` for efficiency.
50
+
The plaintext passphrase file import method will allow you to import all keystores in the `validator_keys` folder encrypted with the same password contained in `password.txt` for efficiency.
64
51
<!-- prettier-ignore-end -->
65
52
66
53
Once imported with either method, these keystores will be automatically loaded when you start the validator. To list the imported keystores, use the `validator list` command.
@@ -118,9 +105,19 @@ Example 3: Setting a `--builder.boostFactor=100` is the same as signaling `--bui
118
105
119
106
### Submit a validator deposit
120
107
121
-
Please use the official Ethereum Launchpad to perform your deposits
108
+
Please use the official Ethereum Launchpad to perform your deposits. Ensure your deposits are sent to the proper beacon chain deposit address on the correct network.
Mar-01 03:09:23.830[] info: Validator seen on beacon chain validatorIndex=1234567, pubKey=0xa6fcfca12e1db6c7341d82327010cd57224dc239d1c5e4fb18286cc32edb877d813c5af1c870d474aef7b3ff7ab927ea
145
+
Mar-01 03:09:23.830[] info: Validator seen on beacon chain validatorIndex=1234568, pubKey=0x8f868e53bbe1451bcf6d42c9ab6d292cbd7fbfa09c59b6b99c1dd6a4977e2e7b4b752c328784ca2788dd6f63ffcbdb7e
0 commit comments