> For the complete documentation index, see [llms.txt](https://ailiquid.gitbook.io/ailiquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ailiquid.gitbook.io/ailiquid-docs/consensus-mechanism.md).

# Consensus Mechanism

Conscious Chain employs its proprietary high-performance Byzantine Fault Tolerant protocol, ConsciousBFT, as the core consensus mechanism of its Layer 1 blockchain. Designed for high-frequency on-chain financial trading, it integrates classical BFT consistency theory with real-world demands for low latency and high throughput, ensuring stability and efficiency under complex transaction loads.

* Sub-second Finality: ConsciousBFT confirms blocks and finalizes transactions in approximately 0.2 seconds, providing a CEX-level user experience.
* High Throughput: The consensus layer supports over 200,000 orders per second, enabling high-frequency applications like on-chain order books (CLOB).
* Byzantine Fault Tolerance: The system tolerates up to one-third of nodes being faulty or malicious, maintaining safety and consistency.
* Dynamic Governance: Initially maintained by core validators, the network will open consensus participation through $CCC staking.
* Jailing Mechanism: Nodes with delayed or abnormal behavior are jailed—suspended from voting and block production to maintain network performance.


---

# 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://ailiquid.gitbook.io/ailiquid-docs/consensus-mechanism.md?ask=<question>&goal=<endgoal>
```

`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.