> 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/disclaimer-and-risk-notice.md). # Disclaimer & Risks This Whitepaper provides information about the purpose, functionality, and ecosystem structure of the D-WAR project and the DWAR token. It is not a prospectus, securities offering document, or contract, and does not constitute an investment recommendation or an offer or solicitation to buy or sell DWAR or any financial instrument. Nothing in this Whitepaper should be interpreted as investment, legal, or tax advice. DWAR is designed as a utility token for accessing content and services, participating in projects and community activities, and receiving utility rewards within the D-WAR ecosystem. Acquiring or holding DWAR does not confer shares, equity, ownership interests, creditor rights, or dividend rights in the project or any associated entity. It does not confer any entitlement to distributions of business revenue, profits, or assets. {% hint style="warning" %} **Participation conditions and variable rewards** Holding DWAR alone does not create an entitlement to interest, dividends, or rewards. Utility rewards are calculated for users who satisfy the applicable project participation conditions, under project-specific criteria relating to participation activities, contribution shares, and on-chain performance. The Reserve Pool is a token allocation structure used to administer user participation rewards, rather than a vehicle for managing investment funds or distributing business profits. Reward availability, amounts, and timing may vary according to applicable conditions and project operating outcomes and are neither fixed nor guaranteed. {% endhint %} Token appreciation, capital protection, redemption, exchange listings, and continued tradability are not guaranteed. Crypto-assets involve risks including significant price volatility, limited liquidity, smart contract vulnerabilities, network failures, hacking, loss of private keys, and regulatory changes. DWAR may lose all of its value or become impossible to sell, and users may lose some or all of the funds used to acquire it. Roadmaps, service launch schedules, projected outcomes, and future plans reflect expectations as of the date of publication. They are not guarantees of results or binding commitments to deliver. They may change or fail to materialize due to development progress, technical constraints, operating conditions, or applicable laws. Charts, examples, and simulations are illustrative and do not guarantee actual performance or future rewards. Users should review the latest official materials, project-specific terms, and relevant risks and make independent decisions. Service availability and eligibility to participate may vary according to jurisdiction and applicable conditions. Independent legal, tax, or financial advice should be sought where appropriate. --- # 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/disclaimer-and-risk-notice.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.