> 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.3-performance-and-scalability.md).

# 4.3 Performance and Scalability

Privacy-preserving systems often suffer from performance limitations due to the cost of cryptographic operations. Xera’s architecture addresses this by carefully separating proof generation from proof verification and by optimizing the verification path within nodes. Proof generation is handled locally by wallets and services; verification, which is far cheaper, is performed by all validating nodes.

Blocks are designed to accommodate multiple shielded transactions while keeping verification costs manageable. Nodes can verify proofs in parallel, exploiting modern multicore hardware. The block size and target block interval are calibrated to balance three requirements: sufficient throughput for practical usage, acceptable confirmation latency, and manageable computational load for validating nodes.

Xera’s fee model and resource rules discourage spam and denial-of-service attacks without imposing prohibitive costs on legitimate usage. Over time, the protocol can integrate more advanced proof systems (for example, recursive proofs or more efficient zk-SNARK constructions) without changing the high-level consensus logic. The network is also compatible with higher-layer scaling strategies, including payment channels, rollups, or dedicated sidechains, provided these preserve the core privacy guarantees of the base layer.


---

# 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.3-performance-and-scalability.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.