> 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-lifecycle/dispute-phase.md).

# Dispute Phase

* After the verification phase ends, the dispute period begins. The minimum time for dispute is 12 hours, and the maximum time is 96 hours.
* Users and High Guards can create a dispute by voting FORE as a ‘dispute fee’ (returned to the dispute creator if the dispute is deemed necessary). The dispute phase has four outcomes:
  * No dispute: validation was correct. 
  * Won A/B: Analysts who validated the wrong outcome lose their NFTs and the FORE locked into it. 
    * Successful dispute: Dispute creator receives dispute fee back and 50% of FORE locked into incorrect Analysts’ NFTs (other 50% is sent to the High Guard). 
    * Unsuccessful dispute: Dispute fee is sent to the High Guard (100%), NFTs and FORE from wrong validators burned.
  * Draw (validation power is equal and not zero): the verifier award is divided equally among the High Guard and the creator of the dispute.
  * Invalid (single sided liquidity or no validation): the Analyst award is divided equally among High Guard and the creator of the dispute.

<figure><img src="https://lh5.googleusercontent.com/KZRAkgGH_r1UKX3NoK7_M0fVeKTYOuo7X40Nd0uh8gLksX0OaML6OTmP96yyS_BR4_V5bp5-46q6d0dfAtlWZ0NkgdR6vOUqHSXZTIE63V2Ju3X_Sqjt6tLBDv_ZMaFQNj00Zvk0--zzBUmDAANmFJjZATY1n8GiHE3sJ2ySxERhg27upo2VvzXcRY5i1g" alt=""><figcaption></figcaption></figure>


---

# 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-lifecycle/dispute-phase.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.