> 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/token-roles-and-utility.md).

# DWAR Token Utility

{% hint style="info" %}
**DWAR utility**

DWAR is a utility token that connects projects and users in the D-WAR ecosystem. Users can use their DWAR Tokens to participate in projects or access content, services, products, events, and community programs. Project participation uses a contribution share based on the amount of DWAR contributed, and utility rewards are calculated from user participation rewards allocated according to on-chain performance.
{% endhint %}

![DWAR Token Utility](https://2078952328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpibjbUiHS5yxzLLvdpX%2Fuploads%2FNnmDDuP17JthrEWWY6Ne%2F5.%20DWAR%20Token%20Roles%20and%20Utility.png?alt=media\&token=464e8b6a-3074-436b-ae72-40046d1c62d1)

The ecosystem is designed for multiple projects to use DWAR as a common means of participation and access. Users can review each project's services and participation policies to select content or projects. Project functions and service regions are described to clarify how users can engage.

Users participate by using the DWAR Tokens they hold. Their contribution share within a project is calculated from the amount of DWAR used to participate, and DWAR utility rewards are received according to that share.


---

# 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/token-roles-and-utility.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.