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