> For the complete documentation index, see [llms.txt](https://d-war.gitbook.io/d-war-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://d-war.gitbook.io/d-war-docs/project-participation-process/dwar-participation-and-rewards.md). # DWAR Participation & Rewards DWAR connects project participation with utility rewards in the D-WAR ecosystem. Users participate in projects such as GAME using their DWAR Tokens and receive DWAR utility rewards according to their contribution shares from user participation rewards allocated based on the project's on-chain performance. {% hint style="info" %} **Project-specific reward allocation** User participation rewards are allocated to the Reserve Pool according to the project's on-chain performance. The contribution share calculated from an individual's DWAR participation amount is applied to these rewards to calculate and distribute the user's utility reward amount. {% endhint %} DWAR received can be used for content, products, and events or participation in other projects, subject to the relevant service conditions. The ecosystem aims to connect project participation and utility rewards with further content use and new project participation. Each project's Reserve Pool manages user participation rewards allocated according to on-chain performance. Participation rewards are expressed in DWAR amounts and linked to project performance, users' contribution shares, and utility reward distribution records. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://d-war.gitbook.io/d-war-docs/project-participation-process/dwar-participation-and-rewards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.