> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/markets/how-are-markets-disputed.md).

# How Are Markets Disputed

Disputes usually happen when:

* a data feed is unavailable or inconsistent at expiry
* an event becomes unclear (e.g., postponed/abandoned match)
* the market rules didn’t cover a rare scenario

In P2P oracle systems, disputes can involve bonding and onchain voting. 0Y uses a simpler user-protection approach: refund on data-quality disputes (for that market).

***

#### 0Y dispute policy (simple)

If there is a dispute due to data quality issues for a specific market, 0Y will:

✅ Refund all traders for that specific market.

Refund means:

* your stake is returned
* no side is considered a winner
* market is marked Refunded / Invalid

***

#### What counts as a “data quality dispute”?

Examples:

* primary source was down at the exact timestamp
* primary and fallback sources disagree materially and rules don’t define tie-break
* upstream provider later confirms an error
* event outcome cannot be verified reliably under the written rules

{% hint style="info" %}
This refund policy is designed to protect beginners. If the “data quality is broken,” nobody should lose money.
{% endhint %}

***

#### Ben’s dispute example (feed outage)

Ben trades a 15-min BTC close market.

At expiry:

* Binance feed is unavailable briefly due to API error
* Result: market is flagged for data-quality review → refund all traders.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.0y.world/markets/how-are-markets-disputed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.