# Introduction Dungeon Arena is built on a transparent and sustainable reward system that balances player incentives with long-term game development. Every SOL spent by Play-to-Earn players fuels the $DUN ecosystem through our buyback and burn mechanism: * **60% Distributed to Players** – Rewards are based on performance in daily events. * **30% Burned** – Permanently reducing the total supply of $DUN. * **10% Allocated to the Team Treasury** – Funding game updates, marketing, and expansion. Our team revenue comes directly from event participation, and we reinvest it into the game’s growth—ensuring continuous updates and marketing to attract new players. However, we do not guarantee that the price of $DUN will always rise; its value is shaped by market dynamics and player engagement. As always, we encourage all players to **Do Your Own Research (DYOR)** before participating. We are committed to evolving Dungeon Arena as long as the community remains active and engaged in events. Future **airdrop campaigns** may be introduced to further reward dedicated players. However, **cheaters will be permanently banned**, and any accumulated rewards in their accounts will be forfeited. Ultimately, the game's updates depend on **community engagement and team revenue**, which is directly influenced by event participation. Your support shapes the future of Dungeon Arena—so **enter the arena, play fair, and become part of the adventure!** --- # Agent Instructions: 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: ``` GET https://dungeon-arena.gitbook.io/dungeon-arena/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.