> 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/ref/storage/consensus-security.md). # Consistency Guarantee As a decentralized distributed system, blockchain uses cryptographic protocols to maintain the consistency of the entire system collaboratively. Byzantine attacks occur when attackers control multiple authorized nodes in a communication network and interfere with or disrupt the network, preventing blockchain nodes from reaching a consensus. On the CESS platform, managing on-chain data may encounter scenarios where nodes maliciously attempt to tamper with or erase data. To address these challenges, the CESS platform incorporates a hybrid and efficient consensus module. The [Random Rotational Selection (R²S)](https://doc.cess.network/ref/in-depth-feat/rrc) consensus mechanism ensures security and system activity as long as the number of Byzantine (malicious) nodes does not exceed a specific threshold. Specifically, when there are f Byzantine nodes in the system, the entire network must maintain at least 3f + 1 replica nodes to ensure that correct decisions are made across the network. This design effectively prevents malicious behavior from being uploaded to the chain, safeguarding the integrity of on-chain data. --- # 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://doc.cess.network/ref/storage/consensus-security.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.