> For the complete documentation index, see [llms.txt](https://docs.fuyo.markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fuyo.markets/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. Fuyo uses a simpler user-protection approach: refund on data-quality disputes (for that market). 

***

#### Fuyo dispute policy (simple)

If there is a dispute due to data quality issues for a specific market, Fuyo 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.