> For the complete documentation index, see [llms.txt](https://docs.zetrix.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zetrix.com/en/architecture/consensus-mechanism/dpos/validator-state-machine.md).
# Validator State Machine
The lifecycle is split into three operational time scales:
* short interval monitoring for validator safety and rotation,
* hourly aggregation for online-presence recording, and
* daily extraction for reward settlement.
This separation matters because not every operational decision is made from the same signal. Sequence lag drives freeze decisions, while accumulated heartbeat presence drives reward eligibility.
### Validator State Model
The validator state machine below captures the functional states used by the system.
#### State semantics
**ACTIVE**
The validator is considered healthy and able to participate in block production. It may also accumulate heartbeat presence that contributes to reward qualification.
**FROZEN**
The validator has been marked abnormal, typically because it is lagging behind the expected chain sequence or failed a forecast-based health check. Frozen validators are excluded from normal participation until recovery conditions are met.
**REWARDED**
This is not a long-lived operational state in the same sense as ACTIVE or FROZEN. It represents the reward-settlement phase in which accumulated eligibility is materialized into token transfers.
---
# 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://docs.zetrix.com/en/architecture/consensus-mechanism/dpos/validator-state-machine.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.