nimbus-eth2/docs/the_nimbus_book/src/voluntary-exit.md

# Perform a voluntary exit

Voluntary exits allow validators to permanently stop performing their duties, and eventually recover the deposit.

Exits are subject to a wait period that depends on the length of the exit queue. While a validator is exiting, it still must perform its duties in order not to lose funds to inactivity penalities.

!!! warning
    Voluntary exits are **irreversible**. You won't be able to validate again with the same key.

    You will also not be able to withdraw your funds until a future hard fork that enables withdrawals.*

!!! note
    Voluntary exits won't be processed if the chain isn't finalising.

To perform a voluntary exit, make sure your beacon node is running with the `--rest` option enabled (e.g. `./run-mainnet-beacon-node.sh --rest`), then run:

    build/nimbus_beacon_node deposits exit --validator=<VALIDATOR_KEYSTORE_PATH>

!!! note
    In the command above, you must replace `<VALIDATOR_KEYSTORE_PATH>` with the file-system path of an Ethereum [ERC-2335 Keystore](https://eips.ethereum.org/EIPS/eip-2335) created by a tool such as [staking-deposit-cli](https://github.com/ethereum/staking-deposit-cli) or [ethdo](https://github.com/wealdtech/ethdo).

## `rest-url` parameter

The `--rest-url` parameter can be used to point the exit command to a specific node for publishing the request, as long as it's compatible with the [REST API](./rest-api.md).
Updates (#2108) 2020-11-30 01:13:47 +00:00			`# Perform a voluntary exit`

REST parameter defaults (#3689) * add default BN for VC * unify "default" beacon node across commands * clean up validator exit docs 2022-06-01 10:47:52 +00:00			`Voluntary exits allow validators to permanently stop performing their duties, and eventually recover the deposit.`

			`Exits are subject to a wait period that depends on the length of the exit queue. While a validator is exiting, it still must perform its duties in order not to lose funds to inactivity penalities.`
Updates (#2108) 2020-11-30 01:13:47 +00:00
Migrate docs to mkdocs (#3900) `mkdocs` works with markdown similar to `mdbook` but is generally more pleasing to the eye and has several nice UX features. This PR does the bulk of the transition - likely, a followup would be needed to fully make use of the extra features and navigation. Book pages have been kept url-compatible, meaning that for the most part, old links should continue to work! Co-authored-by: Etan Kissling <etan@status.im> 2022-07-22 19:47:24 +00:00			`!!! warning`
			`Voluntary exits are irreversible. You won't be able to validate again with the same key.`
update docs (#3890) * update docs * introduce mdbook-admonish for nice looking callouts * new section on data directory * recommend source build for advanced users and direct the rest to binaries * more strongly highlight that execution client is needed * write an actual deposit guide * remove cruft / fix links / etc 2022-07-21 18:19:47 +00:00
Migrate docs to mkdocs (#3900) `mkdocs` works with markdown similar to `mdbook` but is generally more pleasing to the eye and has several nice UX features. This PR does the bulk of the transition - likely, a followup would be needed to fully make use of the extra features and navigation. Book pages have been kept url-compatible, meaning that for the most part, old links should continue to work! Co-authored-by: Etan Kissling <etan@status.im> 2022-07-22 19:47:24 +00:00			`You will also not be able to withdraw your funds until a future hard fork that enables withdrawals.*`
update docs (#3890) * update docs * introduce mdbook-admonish for nice looking callouts * new section on data directory * recommend source build for advanced users and direct the rest to binaries * more strongly highlight that execution client is needed * write an actual deposit guide * remove cruft / fix links / etc 2022-07-21 18:19:47 +00:00
Migrate docs to mkdocs (#3900) `mkdocs` works with markdown similar to `mdbook` but is generally more pleasing to the eye and has several nice UX features. This PR does the bulk of the transition - likely, a followup would be needed to fully make use of the extra features and navigation. Book pages have been kept url-compatible, meaning that for the most part, old links should continue to work! Co-authored-by: Etan Kissling <etan@status.im> 2022-07-22 19:47:24 +00:00			`!!! note`
			`Voluntary exits won't be processed if the chain isn't finalising.`
Updates (#2108) 2020-11-30 01:13:47 +00:00
Some documentation for the new 'deposit exit' work-around 2023-03-21 21:06:40 +00:00			To perform a voluntary exit, make sure your beacon node is running with the `--rest` option enabled (e.g. `./run-mainnet-beacon-node.sh --rest`), then run:
refocus guide around prater 2021-05-22 09:13:27 +00:00
Simplify the validator exit docs further 2023-03-22 00:56:55 +00:00			`build/nimbus_beacon_node deposits exit --validator=<VALIDATOR_KEYSTORE_PATH>`
Migrate docs to mkdocs (#3900) `mkdocs` works with markdown similar to `mdbook` but is generally more pleasing to the eye and has several nice UX features. This PR does the bulk of the transition - likely, a followup would be needed to fully make use of the extra features and navigation. Book pages have been kept url-compatible, meaning that for the most part, old links should continue to work! Co-authored-by: Etan Kissling <etan@status.im> 2022-07-22 19:47:24 +00:00
			`!!! note`
Some documentation for the new 'deposit exit' work-around 2023-03-21 21:06:40 +00:00			In the command above, you must replace `<VALIDATOR_KEYSTORE_PATH>` with the file-system path of an Ethereum [ERC-2335 Keystore](https://eips.ethereum.org/EIPS/eip-2335) created by a tool such as [staking-deposit-cli](https://github.com/ethereum/staking-deposit-cli) or [ethdo](https://github.com/wealdtech/ethdo).
Updates (#2108) 2020-11-30 01:13:47 +00:00
book updates (#3388) 2022-02-14 11:39:10 +00:00			## `rest-url` parameter

REST parameter defaults (#3689) * add default BN for VC * unify "default" beacon node across commands * clean up validator exit docs 2022-06-01 10:47:52 +00:00			The `--rest-url` parameter can be used to point the exit command to a specific node for publishing the request, as long as it's compatible with the [REST API](./rest-api.md).