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

# 市場規則如何澄清

大多數困惑都是因為大家只看了市場標題。在 0Y Markets 上，真正起決定作用的是“規則”部分。

規則通過明確以下內容來消除歧義：

* 結算來源
* 確切的到期時間
* 特殊情況下如何認定

***

#### 如何正確閱讀一個市場（新手方法）

交易前，先快速查看這 4 項：

1. 衡量的是什麼？（價格、比賽結果、官方公告）
2. 什麼時候結算？（時間點 + 時區）
3. 由哪個來源決定？（Binance、Chainlink、聯賽官網）
4. 特殊情況規則？（延期、中止、數據源中斷）


---

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