> For the complete documentation index, see [llms.txt](https://plan-a-labs.gitbook.io/metawara/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plan-a-labs.gitbook.io/metawara/tokenomics.md). # Tokenomics ## Overview The tokenomics of Meta WAR is designed not as a simple distribution mechanism but as a comprehensive system supporting gameplay activity, reward mechanisms, factional conflict, and community sustainability. The core token, $MWAR, serves as the backbone of the ecosystem—directly tied to gameplay, voting, NFT upgrades, betting, and claiming rewards. The total supply of MWAR is capped at 1,000,000,000. The structure minimizes initial circulation while ensuring sufficient liquidity and community participation. A unique feature of the design is its consideration of both presale participant protection and legacy reward integration from the previous project, PESW. More than a utility token, $MWAR is a medium of governance, reward, and competition—connecting in-game decision-making with real-world economic value. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://plan-a-labs.gitbook.io/metawara/tokenomics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.