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