> 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/concepts.md).

# Concepts

- [Architecture](https://docs-old.zus.network/concepts/architecture.md): This document gives an overview of Züs key protocols
- [Mining on the Züs Blockchain](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain.md)
- [Onboarding a New Miner or Sharder](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/onboarding-a-new-miner-or-sharder.md): This page describes how new miners/sharders join the Züs network.
- [Block Production Protocol](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/block-production-protocol.md): This page provides a detailed step-by-step process of our protocol for block production
- [Block Finalization](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/block-finalization.md): This page describe the process of block finalization for the Züs protocol.
- [Merkle Patricia Trees(MPT) and Recovery](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/merkle-patricia-trees-mpt-and-recovery.md): This page provides a more in-depth description of Merkle Patricia Trees (MPT) data structure and how it is used within Züs.
- [View Change and Distributed Key Generation(DKG)](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/view-change-and-distributed-key-generation-dkg.md)
- [Payment](https://docs-old.zus.network/concepts/architecture/payment.md): This page describes how payment works in the Züs network.
- [Storage](https://docs-old.zus.network/concepts/architecture/storage.md)
- [Token Bridge Protocol](https://docs-old.zus.network/concepts/architecture/token-bridge-protocol.md): In this section, we describe our design for transferring ERC-20 tokens for Züs on the Ethereum blockchain to native tokens on the Züs blockchain.
- [Resources](https://docs-old.zus.network/concepts/architecture/resources.md)
- [Tokenomics](https://docs-old.zus.network/concepts/tokenomics.md): ZCN is a Züs Cloud Network cryptocurrency token to buy storage and stake as a service provider.
- [Staking Process](https://docs-old.zus.network/concepts/tokenomics/staking-process.md)
- [Block Rewards](https://docs-old.zus.network/concepts/tokenomics/block-rewards.md)
- [Delegation](https://docs-old.zus.network/concepts/tokenomics/delegation.md)
- [Store](https://docs-old.zus.network/concepts/store.md): Storing data on Züs provides high-performance storage with full ownership of data, complete transparency and privacy.
- [Earn](https://docs-old.zus.network/concepts/earn.md): Rent or turn your unused storage capacity into income by simply connecting to Züs network
- [Build](https://docs-old.zus.network/concepts/build.md): Building on Züs has unparalleled performance, privacy, and security.
- [NFT](https://docs-old.zus.network/concepts/nft.md): Züs Chalk NFT app provides permanent storage for your NFTs.


---

# 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/concepts.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.