> For the complete documentation index, see [llms.txt](https://truemarkets.gitbook.io/truemarkets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://truemarkets.gitbook.io/truemarkets/disputing-outcomes.md).

# Disputing outcomes

In Truemarkets, disputers are basically the same participants as resolvers. Anyone who disagrees with a proposed outcome, can dispute it during the challenge window after it is proposed.

Disputers play a particularly critical role in Truemarkets, they are the stewards of truth.&#x20;

Disputers are the first line of defence for the protocol. They prevent manipulation and ensure that the oracle operates orderly.

By posting a bond equal to that of the resolver, anyone can call the `openDispute` function on a resolution-pending market and provide a `_disputeString` containing the reasons for their dispute.

If the challenge is accepted, the disputer's bond is released and they receive a reward for the successful dispute.

Below is an example image of the data in a dispute transaction on etherscan:

<figure><img src="/files/y8XPk9xqq4OWk3a5LnZ3" alt=""><figcaption></figcaption></figure>

There are three stages of arbitration in Truemarkets, with each escalation being prompted by a dispute.

To challenge an initial proposal, a small bond is required. To dispute an Oracle Council decision, a larger bond must be pledged. Finally, in order to dispute a token holder vote, a wallet with at least 250,000 TRUE tokens (or equivalent vote power) must file a dispute.

Below is an illustration with example values:

<figure><img src="/files/VzeY8rPyiKjAa0ax8GDz" 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://truemarkets.gitbook.io/truemarkets/disputing-outcomes.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.
