> For the complete documentation index, see [llms.txt](https://launchnodes.gitbook.io/exiting-validator-node/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://launchnodes.gitbook.io/exiting-validator-node/exiting-validator-nodes-from-the-beacon-chain-and-withdrawing-multiples-of-32-eth.md).
# Exiting Validator Nodes From the Beacon Chain and withdrawing multiples of 32 ETH
When you want to withdraw your principal 32 ETH from your validator nodes, you must exit your validator node from the Beacon chain and request your Ethereum be returned to the withdrawal address that you used when your nodes were set up or withdrawals were enabled (this address cannot be changed).
These instructions allow you to withdraw your 32 ETH yourself and have your validator nodes join the exit queue. The time taken for your validator node to exit varies and you will be given an estimate once you have exited and it would be reflected on [Beaconcha.in](https://beaconcha.in/)
If you have any questions about these instructions please email your questions to
---
# 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://launchnodes.gitbook.io/exiting-validator-node/exiting-validator-nodes-from-the-beacon-chain-and-withdrawing-multiples-of-32-eth.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.