> For the complete documentation index, see [llms.txt](https://docs-old.zus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.zus.network/products/atlus/charts/zues-explainer.md).

# Züs Explainer

The funnel chart demonstrates the complete hierarchy of storage on the Züs network.

<figure><img src="/files/A2MF12CoWaHcNBoXsue0" alt="" width="563"><figcaption><p>Zus Explainer</p></figcaption></figure>

In summary, these terms provide a comprehensive overview of the storage management system, explaining the concepts of maximum capacity, how stakeholders can support a blobber, the allocation of storage space to clients, and the differentiation between the capacity that has been staked, allocated, and is actively in use.

1. Max Capacity
   * This refers to the total storage capacity that is available on the servers of storage providers. It represents the maximum storage space that these servers can offer to clients or users.
2. Unstaked
   * This represents an opportunity for delegates to stake their resources on a blobber, which is a component of the storage network, until it reaches its maximum capacity.
   * Delegates have the option to allocate their resources to the blobber to support its operations and potentially earn rewards.
3. Staked
   * Staked indicates the amount of storage capacity that has been committed by delegates or stakeholders on a blobber. This means that delegates have chosen to contribute their resources to the blobber's capacity.
4. Unallocated
   * Unallocated capacity is calculated as the difference between the total capacity staked on the blobber and the capacity that has already been allocated to clients.
   * It represents the available free storage space on the blobbers that has not yet been claimed or purchased by clients.
5. Allocated
   * Allocated capacity refers to the storage space that has been locked or reserved by clients when they purchase storage allocations on the blobber.
   * Clients, by allocating capacity, essentially reserve a portion of the blobber's total capacity for their own use.
6. Used
   * Used capacity represents the actual storage space that is currently in use on the server.
   * This space is occupied by data that has been uploaded by clients, and it reflects the portion of the blobber's capacity that is actively being utilized.


---

# 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://docs-old.zus.network/products/atlus/charts/zues-explainer.md?ask=<question>&goal=<endgoal>
```

`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.