> For the complete documentation index, see [llms.txt](https://stader.gitbook.io/stader/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stader.gitbook.io/stader/ethereum/node-operator/permissionless-node-operator/node-registration-and-adding-validators/validator-states.md).

# Validator States

### **Here are the various validator states throughout the entire validator lifecycle:**

1. **Initialized** - Validator undergoing pre-sign and deposit signature verification. Once approved, Stader completes the remaining ETH deposit and adds the validator to the activation queue.
2. **Validator Queued for 28ETH** - Approved validator placed in the queue for 28 ETH.
3. Pending Initialized - Validator received 28 ETH and awaiting deposit processing on the beacon chain.
4. **Pending Queued** - All deposits approved, and the validator is pushed to the beacon chain activation queue.
5. **Active and Ongoing** - Validator actively attesting.
6. **Active and Exiting** - Validator broadcasted exit message.
7. **Exiting and Unslashed** - Unslashed validator pushed to the exit queue.
8. **Active and Slashed** - Validator remains active but has been slashed.
9. **Exiting and Slashed** - Slashed validator pushed to the exit queue.
10. **Withdraw Possible** - Exit withdraw epoch reached, validator awaiting transfer of 32 ETH to the withdraw vault.
11. **Withdraw Done** - 32 ETH sent to the withdraw vault following validator's exit.
12. **Funds Settled** - Validator's share of 4 ETH sent to the claims vault for withdrawal to their Operator reward address.

<br>


---

# 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://stader.gitbook.io/stader/ethereum/node-operator/permissionless-node-operator/node-registration-and-adding-validators/validator-states.md?ask=<question>&goal=<endgoal>
```

`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.