> 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/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/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.