> 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/transparency-and-on-chain-disclosure/verifiable-ecosystem.md). # Verifiable Ecosystem **Project transparency begins with users being able to verify participation records and operating outcomes on-chain.** Contribution shares are calculated from each user's participation amount and activity records, and user participation rewards are allocated according to project performance. The participation records, contribution shares, Reserve Pool reward allocations, and distribution transactions are connected so that users can examine both the calculation process and its results. Records are organized by project and calculation period. Users can follow the sequence from project activity records to contribution calculations, participation reward allocations, and utility reward distribution. When multiple projects operate, their records remain identifiable by project so that participation and progress can be reviewed separately. --- # 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/transparency-and-on-chain-disclosure/verifiable-ecosystem.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.