> 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/tokenomics/delegation.md). # Delegation Any ZCN holder may delegate their tokens to a Service Provider to receive a portion of the Service Provider's earnings. ## **Blobber Delegation** The Züs Cloud Network has an unbounded storage capacity and an unbounded number of participating Blobbers. Since a Blobber with more ZCN staked can receive a larger share of block rewards, an incentive exists to accept outside delegation. A ZCN holder may delegate tokens to any Blobber that is accepting delegation. ## **Miner & Sharder Delegation** For the first phase of pre-mainnet (Fuji), there will be 15 team-operated nodes in the Active Set (10 Miners and 5 Sharders) that can receive delegation from ZCN holders. Each node will have 100 delegation slots. Each slot is comprised of a unique wallet and will have a minimum ZCN staking requirement of 3,000 ZCN and a maximum of 5,000 ZCN per slot. Each node will distribute 100% of earnings to its delegators --- # 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/tokenomics/delegation.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.