> For the complete documentation index, see [llms.txt](https://guide.gameclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.gameclub.com/markets/interactive-blocks.md). # Dispute A dispute is raised when the outcome of a market is unclear, contested, or not yet officially confirmed. GameClub uses a proprietary governance-based resolution system powered by its own token economy. ### How it works When a market reaches its resolution date, a proposed outcome is published. During the dispute window, GameClub token holders can vote directly on the validity of the outcome. The final result is determined by the outcome that receives the majority of votes from token holders, ensuring a decentralized and community-driven resolution process. ### Dispute process 1. Market reaches its resolution date 2. A proposed outcome is published 3. The dispute window opens 4. Token holders cast their votes on the proposed outcome 5. Votes are tallied and the majority outcome is finalized 6. The market is settled and positions are paid out accordingly ### Dispute window * Disputes must be submitted within 24 hours of the proposed outcome being published * Only token holders are eligible to participate in the voting process * For details on voting power and token eligibility, please refer to the Tokenomics section ### Resolution principles All outcomes are determined through community governance. In the event of a tie or insufficient voter participation, positions are settled on a 50/50 basis — each side receives half of the total payout regardless of the proposed outcome. > ![:전구:](https://a.slack-edge.com/production-standard-emoji-assets/15.0/google-medium/1f4a1.png) GameClub's dispute resolution is governed entirely by its token holders — ensuring fair, transparent, and decentralized settlement without reliance on any third-party protocol. --- # 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://guide.gameclub.com/markets/interactive-blocks.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.