> For the complete documentation index, see [llms.txt](https://docs.foreprotocol.io/fore-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foreprotocol.io/fore-protocol/whitepaper/how-fore-works/protocol-roles/dispute-resolution.md).

# Dispute Resolution

If market participants disagree on an outcome, FORE has created an innovative dispute resolution mechanism that allows for a final check and referees. While any user can be a dispute creator, the High Guard is a collective of active Analysts with Black NFTs (the highest tier) who have proven their loyalty to the community and the protocol. Dispute creators and High Guards work together to perform dispute resolution roles, are responsible for making sure that Analysts are accurately validating outcomes, and hold each other group accountable. This mechanism provides market participants with a way to report any violations or concerns they have about markets and/or their results. Dispute creators and High Guards are likely to step in where they see mispriced odds, bringing odds closer to reflect reality. This change in odds may drive greater activity in the secondary market, as existing market participants no longer find their market proportion (and its potential payout) appealing. These users also step in when they see inaccurately titled, timed, or validated markets, ensuring the overall quality of the markets (and user experience) on FORE Predict.


---

# 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.foreprotocol.io/fore-protocol/whitepaper/how-fore-works/protocol-roles/dispute-resolution.md?ask=<question>&goal=<endgoal>
```

`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.
