> For the complete documentation index, see [llms.txt](https://kashed.gitbook.io/kashed-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kashed.gitbook.io/kashed-docs/tokenomics.md). # Tokenomics ### $KASH $KASH is the native utility token powering the Kashed ecosystem. The token has a fixed supply of 1,000,000,000 $KASH #### Rewards Pool 20% of the total supply (200,000,000 $KASH) is allocated to the Rewards Pool at launch. All in-game reward emissions originate from this allocation. #### Deflationary Mechanics Certain in-game actions require spending $KASH, with a portion of tokens permanently removed from circulation through burn mechanics. As player activity increases, token consumption and network participation become core components of the ecosystem. #### Referrals Kashed includes a referral system designed to encourage community-driven growth. Players can invite others into the ecosystem and participate in the expansion of the network through referral-based incentives. Additional details regarding allocations, emissions, and ecosystem mechanics will be published prior to launch. --- # 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://kashed.gitbook.io/kashed-docs/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.