> 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/zh-tw/shi-chang/how-are-markets-disputed.md).

# 市場爭議如何處理

爭議通常發生在以下情況：

* 到期時數據源不可用或數據不一致
* 事件變得不明確（例如比賽延期/中止）
* 市場規則沒有涵蓋某種罕見情況

在 P2P 預言機系統中，爭議處理可能涉及繳納保證金和鏈上投票。0Y 採用更簡單、以保護用戶為先的方式：出現數據質量爭議時，對該市場進行退款。

***

#### 0Y 爭議政策（簡版）

如果某個市場因數據質量問題出現爭議，0Y 會：

✅ 向該市場的所有交易者退款。

退款意味著：

* 你的本金會被退還
* 沒有任何一方被認定為獲勝方
* 市場被標記為“已退款 / 無效”

***

#### 什麼算“數據質量爭議”？

例如：

* 主要數據來源在確切的時間點宕機
* 主要來源和備用來源的數據存在實質性差異，且規則沒有規定如何裁定
* 上游提供商事後確認數據有誤
* 按照書面規則無法可靠地核實事件結果

{% hint style="info" %}
這項退款政策旨在保護新手。如果“數據質量出了問題”，就不應該有人因此虧錢。
{% endhint %}

***

#### Ben 的爭議示例（數據源中斷）

Ben 交易了一個 BTC 15 分鐘收盤市場。

到期時：

* 由於 API 錯誤，Binance 數據源短暫不可用
* 結果：該市場被標記進行數據質量審查 → 向所有交易者退款。


---

# 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/zh-tw/shi-chang/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.