> For the complete documentation index, see [llms.txt](https://docs.openpeer.xyz/openpeer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openpeer.xyz/openpeer-docs/dispute-resolution/handling-disputes.md).

# Handling Disputes

Both parties will have 24 hours from the time a dispute is opened to submit evidence. They will also need to pay a small \~$1 fee in the native currency of the chain they are trading on. For example on Polygon the dispute fee is 1 MATIC.

Once evidence is submitted, the OpenPeer team arbitrates the dispute resolution by reviewing the information submitted by each side and awarding the cryptocurrencies still in escrow to the correct party.

In the future the arbitration process will be decentralised to the OpenPeer token holders. This will lead to greater decentralisation of the platform and token, and make OpenPeer more resilient. 


---

# 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.openpeer.xyz/openpeer-docs/dispute-resolution/handling-disputes.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.