> For the complete documentation index, see [llms.txt](https://docs.staking.galaxy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.staking.galaxy.com/ethereum/validator-statuses.md).

# Validator Statuses

| Status             | Description                                                                                                                                               |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| STAKING\_INITIATED | A staking request has been successfully received by the platform.                                                                                         |
| REJECTED           | The staking request has been rejected by the Staking Engine. All validators created as part of that staking request will receive this status.             |
| PENDING\_DEPOSIT   | Once the staking request is successfully processed and validators are commissioned, clients are expected to deposit their assets to the relevant address. |
| DEPOSITED          | The validator has entered the Pending Deposit Queue and has met the minimum balance requirement for activation (32 ETH).                                  |
| DEPOSIT\_FAILED    | The validator has not been funded within the pre-defined time period.                                                                                     |
| PENDING\_QUEUED    | The validator has been successfully funded and added to the activation queue.                                                                             |
| ACTIVE             | The validator is active and earning rewards.                                                                                                              |
| SLASHING           | The validator is online but has been identified as malicious and incurred penalties, and scheduled to exit.                                               |
| SLASHED            | The validator has been kicked out of the network after reaching the exit epoch due to slashing.                                                           |
| EXIT\_INITIATED    | An exit request has been successfully received by the platform.                                                                                           |
| EXITING            | The validator is online and currently exiting the network.                                                                                                |
| EXITED             | The validator has been removed from the network.                                                                                                          |
| WITHDRAWABLE       | The validator has reached the withdrawable epoch after a successful exit.                                                                                 |
| WITHDRAWN          | The funds have been returned to the withdrawal address provided for the validator.                                                                        |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.staking.galaxy.com/ethereum/validator-statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
