> 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/performance-and-utility-rewards.md).

# Performance & Utility Rewards

{% hint style="info" %}
**Participation model**

Users participate in individual projects such as GAME using their DWAR Tokens. User participation rewards are allocated to the Reserve Pool according to the project's on-chain performance. Users receive utility rewards based on their contribution share, calculated from the amount of DWAR used to participate.
{% endhint %}

The amount of DWAR used to participate provides the basis for calculating a user's contribution share in a project. This share is the user's participation amount divided by the total project participation amount. Each project's Reserve Pool manages user participation rewards and connects on-chain performance, reward allocations, participation status, and utility reward records.

![DWAR Project Participation Process](https://2078952328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpibjbUiHS5yxzLLvdpX%2Fuploads%2FkXGxsOcqI9HDvFqrEpbS%2F6.1%20On-chain%20Performance%20and%20Utility%20Rewards.png?alt=media\&token=d6b2e7bb-5cf3-4819-8307-b97ce39f598e)


---

# 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/performance-and-utility-rewards.md?ask=<question>&goal=<user_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.