> For the complete documentation index, see [llms.txt](https://doc.cess.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cess.network/cess-miners/consensus-miner.md). # Consensus Nodes **Consensus Node** is a fundamental role within the CESS ecosystem, responsible for supporting the security and integrity of the CESS network. By running the CESS blockchain client, Consensus Nodes participate in the consensus mechanism, helping to validate transactions and secure the decentralized infrastructure. As key contributors to the network's governance and stability, Consensus Nodes play a critical role in maintaining the distributed ledger, ensuring that the data stored within the CESS network is both accurate and tamper-proof. Their activities include validating blocks, verifying the correctness of transactions, and participating in the protocol's decision-making processes, ultimately ensuring the CESS network's overall resilience and scalability. Read about [how to run a consensus node client](/cess-miners/consensus-miner/running.md), or check to learn how [the miner is rewarded](/cess-miners/consensus-miner/reward.md). Refer to the [troubleshooting guide](/cess-miners/storage-miner/troubleshooting.md) if you encounter any problem. --- # 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://doc.cess.network/cess-miners/consensus-miner.md?ask=&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.