> For the complete documentation index, see [llms.txt](https://blocx.gitbook.io/blocx./llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blocx.gitbook.io/blocx./validator-node/exiting-the-validator-node.md).
# Exiting the Validator Node
### Exiting Validator Node
### **Important Considerations Before Exiting**
* **Irreversibility**: Once a validator is exited, it cannot be reactivated. To resume staking, you'd need to generate new validator keys and initiate the staking process anew.
* **Withdrawal Credentials**: Ensure your validator's withdrawal credentials are set to type `0x01`. This setting is necessary for automatic withdrawals. If your credentials are of type `0x00` (BLS), you'll need to update them before exiting.
### **Access the Validator Container**
Run this command to open an interactive shell inside the validator container:
```bash
docker exec -it $(docker ps --filter "name=validator" --format "{{.Names}}") bash
```
### **Locate the Specific Keystore**
List your validator keys to identify the correct directory:
```bash
ls /validator_keys/
```
\
You will see folders like:
```bash
0xd76cb34a345c8543640ffded77335de1c78d6e6856ea1c8129bc00086147d6479f653fdebf5bc5e92e2720e9f3632441
```
### Run the Voluntary Exit Command
Use the full path to your voting-keystore.json in the command:
```bash
lighthouse account validator exit --testnet-dir=/el-cl-genesis-data/custom_config_data --keystore /validator_keys//voting-keystore.json --beacon-node http://beacon:5052
```
Example:
```bash
lighthouse account validator exit --testnet-dir=/el-cl-genesis-data/custom_config_data --keystore /validator_keys/0xd76cb34a3.../voting-keystore.json --beacon-node http://beacon:5052
```
### **Provide the Validator Password**
When prompted:
Enter the keystore password for validator...
```bash
→ Type the password you set when you created the validator.
```
### **Provide the Exit Phrase**
It will then prompt:
Enter the exit phrase from the above URL to confirm the voluntary exit:
→ Type exactly:
```bash
Exit my validator
```
### **Verifying the Exit Status**
To monitor the status of your validator's exit, you can use [beacon.blocxscan.com](http://beacon.blocxscan.com/)
1. Navigate to .
2. Enter your validator's public key or index in the search bar.
3. Review the validator's status to confirm the exit process.
### **Summary of Flow:**
* Access container → list keys → run command → enter validator password → type exit phrase → done!
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://blocx.gitbook.io/blocx./validator-node/exiting-the-validator-node.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.