> 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.1-network-topology.md).

# 4.1 Network Topology

The Xera protocol operates on a fully decentralized peer-to-peer network. Any participant can run a xerad node and join the network without permission. Nodes maintain persistent connections to a set of peers, propagating blocks, transactions, and relevant metadata. There is no central routing point or privileged relay; instead, the network relies on redundancy and randomization in peer selection to resist censorship and single points of failure.

Each full node stores the canonical ledger, which consists of encrypted commitments, nullifiers, headers, and consensus metadata instead of plaintext account balances. Nodes verify incoming blocks, ensure the validity of zero-knowledge proofs, and reject any state transitions that violate protocol rules. Even though they participate in block validation, nodes do not gain access to sensitive information such as sender addresses, receiver addresses, or transaction amounts. The network thus separates state correctness from data visibility.

To support a broad range of devices, the network accommodates both full nodes and lightweight clients. Full nodes retain the complete history and are best suited for infrastructure providers, exchanges, and high-availability services. Light clients rely on simplified verification techniques, checkpointing, or interactions with trusted or semi-trusted full nodes to obtain relevant state proofs. This architecture allows mobile and resource-constrained environments to participate in the Xera ecosystem without undermining decentralization.


---

# 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.1-network-topology.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.