> For the complete documentation index, see [llms.txt](https://whitepaper.minxtoken.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.minxtoken.io/distribution-and-token-economics.md). # Distribution and Token Economics The MINX Token adopts a player-focused economy, prioritizing sustainability. This structure is designed not only as a reward mechanism but also as the primary value carrier of the platform. #### Reward Ecosystem * **In-Game Purchases**: Players’ in-game purchases, entry fees, and event tickets directly contribute to reward pools. * **Sponsor Contributions**: Revenue from brand and partnership sponsorships supports tournament and reward pools. * **Leaderboards and Task-Based Rewards**: Reward distribution is transparent and performance-based, relying on participation and achievement mechanisms. #### Deflationary Structure * **Token Supply Control**: The MINX Token is launched with a limited total supply. * **Non-Treasury-Dependent Reward Model**: Rewards are sourced directly from the game economy and sponsors, reducing pressure on the token and preserving its value. #### Token Utility * Tournament entry fees. * In-game purchases. * NFT trading and collectibles marketplace. * Unlocking systems. * Daily tasks and premium access within the Mini App. --- # 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://whitepaper.minxtoken.io/distribution-and-token-economics.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.