Skip to content

Commit

Permalink
update voluntary exit in Node
Browse files Browse the repository at this point in the history
  • Loading branch information
zengzengzenghuy committed Sep 7, 2023
1 parent 55254c6 commit dfaa661
Showing 1 changed file with 9 additions and 12 deletions.
21 changes: 9 additions & 12 deletions docs/node/management/voluntary-exit.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Voluntary Exit

If you decide to stop validating and disable your node, you can initiate a voluntary exit. This will freeze your balance at its current value (rewards and/or penalties will no longer accrue).

If you perform a voluntary exit, you **will not be able to withdraw your balance** until the Shapella hardfork is complete.
If you initiates a voluntary exit, your validator will receive the full staked funds to the withdrawal address, provided that the validator has [withdrawal credentials](withdrawals.md#check-withdrawal-credential) of type `0x01`.

Voluntary exit procedures vary depending on your client.

Expand All @@ -20,8 +20,7 @@ In order to initiate an exit, users can use the lighthouse account validator exi
lighthouse --network gnosis account validator exit --keystore /path/to/keystore --beacon-node http://consensus:5052
```

* For more info, see the [Lighthouse Voluntary Exit docs](https://lighthouse-book.sigmaprime.io/voluntary-exit.html).

- For more info, see the [Lighthouse Voluntary Exit docs](https://lighthouse-book.sigmaprime.io/voluntary-exit.html).

### Lodestar

Expand All @@ -31,29 +30,27 @@ Follow the syntax of the Lodestar CLI commands and their options.
validator voluntary-exit --network gnosis --publicKey 0xF00
```

* For more info, see the [Lodestar Command Line Reference doc](https://chainsafe.github.io/lodestar/reference/cli/#validator-voluntary-exit).

- For more info, see the [Lodestar Command Line Reference doc](https://chainsafe.github.io/lodestar/reference/cli/#validator-voluntary-exit).

### Nimbus

To perform a voluntary exit, make sure your beacon node is running, then run:
To perform a voluntary exit, make sure your beacon node is running with the `--rest` option enabled, then run:

```bash
build/nimbus_beacon_node deposits exit --data-dir=build/data/shared_gnosis_0 --validator=<VALIDATOR_PUBLIC_KEY>
```

* For more info, see the Nimbus [Perform a voluntary exit](https://nimbus.guide/voluntary-exit.html) docs.

- For more info, see the Nimbus [Perform a voluntary exit](https://nimbus.guide/voluntary-exit.html) docs.

### Prysm

Login to your node and use the following command to request a voluntary exit. Replace \<PUBKEY\_1> with each public key you want to exit.
Use [prysmctl tool](https://docs.prylabs.network/docs/prysm-usage/prysmctl) to voluntarily exit your validator.

```bash
prysm.sh validator accounts voluntary-exit
prysmctl validator exit --wallet-dir=<path/to/wallet> --beacon-rpc-provider=<127.0.0.1:4000>
```

* For more info, see the Prysm [Exit your validator](https://docs.prylabs.network/docs/wallet/exiting-a-validator/) doc.
- For more info, see the Prysm [Exit your validator](https://docs.prylabs.network/docs/wallet/exiting-a-validator/) doc.

### Teku

Expand All @@ -64,4 +61,4 @@ teku voluntary-exit --beacon-node-api-endpoint=http://consensus:5051 \
--validator-keys=validator/keys/validator_ABC.json:validator/passwords/validator_ABC.txt
```

* For more info, see the Teku [Voluntarily exit a validator](https://docs.teku.consensys.net/en/latest/HowTo/Voluntary-Exit/) docs.
- For more info, see the Teku [Voluntarily exit a validator](https://docs.teku.consensys.net/how-to/voluntarily-exit#:~:text=A%20voluntary%20exit%20is%20when,successfully%20exited%20to%20avoid%20penalties.) docs.

0 comments on commit dfaa661

Please sign in to comment.