> 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/ecosystem-and-project-structure/on-chain-performance.md). # On-chain Performance Project performance is based on its on-chain activity and records. Participation activities and service use defined by each project are linked to on-chain records, which provide a basis for reviewing project progress and participation. {% hint style="info" %} **From performance to utility rewards** On-chain performance provides a reference for project participation and service activity. User participation rewards are allocated to the Reserve Pool according to the performance criteria established by the project. Users' participation contribution shares are then applied to calculate DWAR utility rewards. {% endhint %} Each project connects on-chain activity records, participation amounts, and Reserve Pool participation reward allocations. Users can review these records to follow the progress of their projects and their utility reward history. --- # 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/ecosystem-and-project-structure/on-chain-performance.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.