> 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-resolved.md).

# 市场如何结算

0Y Markets 使用可靠的外部数据来源对市场进行结算，例如：

* Binance 实时行情 API 数据
* Chainlink 数据流
* 其他第三方提供商（视市场类型而定）

到期时，0Y Markets 会根据市场定义的规则（例如“某一时间点的价格”）确认结果。

{% hint style="info" %}
市场在到期时自动结算——你无需进行任何操作。
{% endhint %}

***

#### 结算结果（接下来会发生什么）

市场最终确定后：

* 获胜方的赔付计入钱包余额
* 失败方的投注金额不予退还
* 市场被标记为“已结算”

（与 P2P 系统不同，这里没有由用户提议结算并缴纳保证金的流程；0Y Markets 根据预先定义的规则和数据来源集中进行结算。）

***

#### Ben 的结算示例（明确的时间点）

市场：“BTC 在 UTC 12:00:00 收盘价高于 50,000”

* 在 UTC 12:00:00，0Y Markets 检查规定的数据来源
* 如果收盘价为 50,120 → YES 获胜
* 如果为 49,980 → NO 获胜


---

# 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-resolved.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.