> For the complete documentation index, see [llms.txt](https://docs.aces.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aces.fun/why-aces.fun-will-dominate-the-current-meta/game-theory.md). # Game Theory Traditional memecoin dynamics follow the Prisoner's Dilemma - while collective holding benefits everyone, individual incentives drive early selling. Traders operate on a simple premise: sell first or miss profits. This creates a self-fulfilling cycle where the fear of others selling leads to widespread selling behavior. ACES.fun transforms this dynamic through our Community Reward. When traders know a significant reward awaits at the point of asset sale, the calculation shifts fundamentally. Rather than racing to sell first, holders gain advantage by maintaining their position. If others sell, the remaining holders capture a larger share of the eventual reward. This creates natural resistance to selling pressure and encourages longer-term holding. --- # 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.aces.fun/why-aces.fun-will-dominate-the-current-meta/game-theory.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.