> 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/1.-introduction/1.2-core-objectives-of-xera.md).

# 1.2 Core Objectives of Xera

Xera’s design begins with a simple premise: digital money must provide confidentiality as a default state, not as an optional feature. Privacy enforced by cryptography—rather than policy or institutional promises—ensures that individuals regain control over their financial information. Zero-knowledge proofs allow each transaction to be verified for correctness without revealing its contents, enabling the system to remain both private and trustless.

At the same time, Xera must retain the verifiability that defines decentralized systems. The protocol replaces explicit inputs and outputs with commitments, nullifiers, and encrypted notes, ensuring that nodes can validate correctness without observing sensitive details. This architecture creates a clear separation between public consensus rules and private state transitions, allowing the network to operate transparently while individual actions remain confidential.

Usability is a critical requirement for any privacy-preserving system. Complex address formats, manual privacy toggles, and fragile workflows discourage adoption. Xera introduces a unified address system that enables users to receive both transparent and shielded transactions without understanding underlying distinctions. Wallets automate proof generation, key management, and scanning logic, reducing cognitive burden and minimizing privacy leaks.

Xera therefore addresses three structural goals:

* Default confidentiality through zero-knowledge proofs.
* Public verifiability through decentralized consensus.
* Mainstream usability through unified address abstraction.


---

# 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/1.-introduction/1.2-core-objectives-of-xera.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.