> For the complete documentation index, see [llms.txt](https://docs.xeratoken.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xeratoken.xyz/4.-network-and-consensus/4.2-consensus-mechanism-and-security-model.md).

# 4.2 Consensus Mechanism and Security Model

Xera’s consensus layer is designed to ensure deterministic validation of the global state while remaining agnostic to transaction content. Whether implemented as Proof-of-Stake or a related variant, the consensus mechanism must satisfy three core properties:

* Permissionless participation: any entity can join, validate, and propose blocks subject only to protocol rules.
* Economic robustness: it should be economically infeasible for an attacker to gain sustained control over block production.
* Deterministic verification: nodes must independently reach the same view of valid blocks and chain history.

Blocks in Xera contain zero-knowledge proofs that attest to the validity of private transactions. A block is considered valid only if all included proofs verify successfully against the current state. This requirement tightly couples the privacy layer with the consensus layer: consensus does not rely on trust in transaction creators, but on the cryptographic soundness of their proofs. The consensus engine treats shielded state transitions as opaque from a data perspective but fully constrained from a rules perspective.

The protocol assumes that an adversary cannot consistently control the majority of consensus weight or network connectivity. Under this assumption, Xera provides both safety (honest nodes agree on finalized state) and liveness (valid transactions are eventually included). In pathological conditions—such as network partitions or suspected attacks—the protocol favors preserving safety over short-term throughput. Finality rules and chain selection strategies are chosen to minimize the risk of state reversion while retaining reasonable block times.


---

# 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:

```
GET https://docs.xeratoken.xyz/4.-network-and-consensus/4.2-consensus-mechanism-and-security-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.