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: book/src/validator-manager-api.md
+76-1Lines changed: 76 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,75 @@
1
1
# Managing Validators
2
2
3
-
The `lighthouse validator-manager` uses the [Keymanager API](https://ethereum.github.io/keymanager-APIs/#/) to list, import and delete keystores via the HTTP API. This requires the validator client running with the flag `--http`.
3
+
The `lighthouse validator-manager` uses the [Keymanager API](https://ethereum.github.io/keymanager-APIs/#/) to exit, list, import and delete keystores via the HTTP API. This requires the validator client running with the flag `--http`.
4
+
5
+
## Exit
6
+
7
+
The `exit` command exits one or more validators from the validator client. To `exit`:
8
+
9
+
> **Important note: Once the --beacon-node flag is used, it will publish the voluntary exit to the network. This action is irreversible.**
10
+
11
+
```bash
12
+
lighthouse vm exit --vc-token <API-TOKEN-PATH> --validators pubkey1,pubkey2 --beacon-node http://beacon-node-url:5052
13
+
```
14
+
15
+
Example:
16
+
17
+
```bash
18
+
lighthouse vm exit --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators 0x8885c29b8f88ee9b9a37b480fd4384fed74bda33d85bc8171a904847e65688b6c9bb4362d6597fd30109fb2def6c3ae4,0xa262dae3dcd2b2e280af534effa16bedb27c06f2959e114d53bd2a248ca324a018dc73179899a066149471a94a1bc92f --beacon-node http://localhost:5052
19
+
```
20
+
21
+
If successful, the following message will be returned:
22
+
23
+
```text
24
+
Successfully validated and published voluntary exit for validator 0x8885c29b8f88ee9b9a37b480fd4384fed74bda33d85bc8171a904847e65688b6c9bb4362d6597fd30109fb2def6c3ae4
25
+
Successfully validated and published voluntary exit for validator
To exit all validators on the validator client, use the keyword `all`:
30
+
31
+
```bash
32
+
lighthouse vm exit --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators all --beacon-node http://localhost:5052
33
+
```
34
+
35
+
To check the voluntary exit status, use both `--status` and `--beacon-node` flags:
36
+
37
+
```bash
38
+
lighthouse vm exit --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators 0x8de7ec501d574152f52a962bf588573df2fc3563fd0c6077651208ed20f24f3d8572425706b343117b48bdca56808416 --beacon-node http://localhost:5052 --status
39
+
```
40
+
41
+
If the validator voluntary exit has been accepted by the chain, the following message will be returned:
42
+
43
+
```text
44
+
Voluntary exit for validator 0x8de7ec501d574152f52a962bf588573df2fc3563fd0c6077651208ed20f24f3d8572425706b343117b48bdca56808416 has been accepted into the beacon chain, but not yet finalized. Finalization may take several minutes or longer. Before finalization there is a low probability that the exit may be reverted.
45
+
Current epoch: 2, Exit epoch: 7, Withdrawable epoch: 263
46
+
Please keep your validator running till exit epoch
47
+
Exit epoch in approximately 480 secs
48
+
```
49
+
50
+
When the exit epoch is reached, querying the status will return:
51
+
52
+
```text
53
+
Validator 0x8de7ec501d574152f52a962bf588573df2fc3563fd0c6077651208ed20f24f3d8572425706b343117b48bdca56808416 has exited at epoch: 7
54
+
```
55
+
56
+
You can safely shut down the validator client at this point.
57
+
58
+
The following exit command will only generate the exit message and will not publish the message to the network, i.e., there will be no voluntary exit.
59
+
60
+
To only generate the exit message without publishing it to the network, use the flag `--signature`:
61
+
62
+
```bash
63
+
lighthouse vm exit --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators all --signature
64
+
```
65
+
66
+
To generate the exit message for a particular (future) epoch, use the flag `--exit-epoch`:
67
+
68
+
```bash
69
+
lighthouse vm exit --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators all --signature --exit-epoch 1234567
70
+
```
71
+
72
+
The generated exit message will only be valid at or after the specified exit-epoch, in this case, epoch 1234567.
4
73
5
74
## Delete
6
75
@@ -16,6 +85,12 @@ Example:
16
85
lighthouse vm delete --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators 0x8885c29b8f88ee9b9a37b480fd4384fed74bda33d85bc8171a904847e65688b6c9bb4362d6597fd30109fb2def6c3ae4,0xa262dae3dcd2b2e280af534effa16bedb27c06f2959e114d53bd2a248ca324a018dc73179899a066149471a94a1bc92f
17
86
```
18
87
88
+
To delete all validators on the validator client, use the keyword `all`:
89
+
90
+
```bash
91
+
lighthouse vm delete --vc-token ~/.lighthouse/mainnet/validators/api-token.txt --validators all
92
+
```
93
+
19
94
## Import
20
95
21
96
The `import` command imports validator keystores generated by the staking-deposit-cli/ethstaker-deposit-cli. To import a validator keystore:
Copy file name to clipboardExpand all lines: book/src/voluntary-exit.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ A validator can initiate a voluntary exit provided that the validator is current
10
10
It takes at a minimum 5 epochs (32 minutes) for a validator to exit after initiating a voluntary exit.
11
11
This number can be much higher depending on how many other validators are queued to exit.
12
12
13
+
You can also perform voluntary exit for one or more validators using the validator manager, see [Managing Validators](./validator-manager-api.md#exit) for more details.
14
+
13
15
## Initiating a voluntary exit
14
16
15
17
In order to initiate an exit, users can use the `lighthouse account validator exit` command.
0 commit comments