> For the complete documentation index, see [llms.txt](https://whitepaper.zbyte.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.zbyte.io/tokenomics/staking.md). # Staking Within the dynamic zbyte ecosystem, participants have the opportunity to engage in staking, a process where they commit their assets to endorse decentralized applications (dApps) crafted on the dPlat and available on the dApp store. The rewards from staking are thoughtfully distributed between the dApp developer and the users, forming a symbiotic relationship. This means that developers are not only encouraged but directly incentivized to design and introduce applications that users genuinely find valuable and engaging. This collaborative model fosters a thriving environment where the interests of developers and users align, creating a symbiosis that drives the development of high-quality, user-centric dApps. As users contribute to the staking process, they actively play a role in the success of the applications they appreciate. This intricate interplay of incentives enhances the overall vibrancy of the ecosystem, ensuring that the rewards generated from staking are shared among those who actively contribute to and appreciate the burgeoning decentralized application landscape within the zbyte ecosystem. --- # 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://whitepaper.zbyte.io/tokenomics/staking.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.