> 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/2.-protocol-overview/2.1-system-architecture.md).

# 2.1 System Architecture

Xera employs a layered protocol architecture that cleanly separates networking, transaction logic, privacy mechanisms, and application interfaces. The network layer is responsible for block propagation, consensus participation, and state replication. It ensures decentralization by allowing any participant to join and validate the protocol independently. This layer maintains deterministic rules and enforces protocol correctness across all nodes.

The transaction layer defines how value is represented in the system. Instead of exposing inputs and outputs publicly, Xera encodes transfers using commitments and nullifiers. These structures support transparent, shielded, and hybrid transfers, allowing the protocol to balance confidentiality with compatibility. State transitions update the ledger without revealing internal details, maintaining a consistent and verifiable global state.

A dedicated privacy layer manages zero-knowledge proof construction and verification. Wallets generate proofs to demonstrate ownership and balance correctness, while nodes verify these proofs efficiently without access to sensitive data. This layer is modular and proof-system agnostic, enabling future upgrades to more efficient cryptographic schemes.

The application layer provides a unified developer interface through SDKs, APIs, and wallet abstractions. It exposes a simplified model for value transfers, making integration possible without deep knowledge of cryptography or protocol internals. This separation of concerns allows the protocol to evolve while preserving compatibility.


---

# 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/2.-protocol-overview/2.1-system-architecture.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.