> For the complete documentation index, see [llms.txt](https://docs.trueopen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trueopen.ai/operators/validators.md). # Validators Consensus, governance, and security responsibilities of a TrueOpen Validator. Validators operate the chain's consensus and deterministic application state machine. Their role makes accepted protocol state available to Users, Builders, and Cortex Nodes. ## Responsibilities * Validate transactions and execute the versioned state-transition rules consistently. * Verify the required proposer VRF beacon and maintain the separately registered VRF key. * Maintain consensus-key custody and distinguish it from account, service, VRF, and bridge-signing keys. * Participate in the governed Validator-set and upgrade processes. * Follow bridge signer coordination and freeze controls when membership changes affect the canonical asset route. Consensus stake and service liability are separate. Running a Validator does not automatically provide inference or verification capacity, and ordinary service faults do not debit consensus stake. ## Operating boundaries Operators need synchronized chain state, durable node storage, protected signing infrastructure, and an upgrade process compatible with the active network version. Public installation commands, genesis values, and network endpoints will be documented with supported releases. Read [Randomness](/protocol/v1/randomness.md), [Governance](/protocol/v1/governance.md), and [Cross-chain assets](/protocol/v1/cross-chain-assets.md) before operating the corresponding duties. --- # 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.trueopen.ai/operators/validators.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.