> For the complete documentation index, see [llms.txt](https://000z.gitbook.io/0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://000z.gitbook.io/0/architecture/network-overview.md).
# Network Overview
At a high level the network is made up of "Incentivized Servers" that are responsible for all the networking functionality, cryptographic operations, validation, scalability and security of the network and ensure that users privacy and anonymity is guaranteed even if the entire network is observed by adversaries.
* **Targeted Distribution**: A bonded-stake ratio will be identified based on the number of desired servers in the network to encourage scaling and decentralization (ideally above 500).
* **Dynamic Inflation**: Inflation will dynamically adjust based on the moving change rate tied to an optimal number of servers in the network. If the actual % bonded is below the target, the inflation rate should increase to encourage more staking--servers. Conversely, if the % bonded is above the target, the inflation rate should decrease to discourage excessive inflation.
* The servers are organized into a network of *L* layers and users’ messages are routed by servers from one layer to the next.
* The network is organized in two stages. A one-time path establishment stage followed by a repeated message broadcasting stage.
* The mix-net is bookended by anytrust groups to prevent denial-of-service attacks at the entry and exit points. (*anytrust groups are a group of randomly selected servers from the network*)
* In both stages, the network resolves failures and attacks by malicious users and servers through on-demand blame protocols.
---
# 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, and the optional `goal` query parameter:
```
GET https://000z.gitbook.io/0/architecture/network-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.