> For the complete documentation index, see [llms.txt](https://docs.milliononmars.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milliononmars.com/whitepaper/glitter-tokenomics/gameplay-rewards.md). # Gameplay Rewards 250M Glitter Tokens (25%) are dedicated to the rewarding players for Gameplay of the Million on Mars Metaverse. These tokens are to stimulate player growth and engagement to cause growth. These tokens will also be distributed to various marketing efforts such as air drops and giveaways. The team will balance growth of the project vs maintaining the Glitter token value. A key KPI for the team will be to maintain Glitter at stable value and enjoy moderate growth over time. #### Planned Play & Own Token Budget Items * Founder Token Rewards - 5.1M * Martizens Bankroll Rewards - 6.2M * In-game rewards for the whole variety of game systems, via leaderboards and loot tables * Compensated Streamers and Podcasts * Airdrops, Giveaways and Prizes * Referral Rewards --- # 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://docs.milliononmars.com/whitepaper/glitter-tokenomics/gameplay-rewards.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.