> 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/ru-men-zhi-nan/how-you-can-profit.md).

# 如何獲利？

當市場結算時，如果你選擇的結果是正確的，你就能獲利。

#### Alice 的例子

Alice 認為 BTC 短期內會上漲。

* 市場：“BTC 15 分鐘收盤：看漲還是看跌？”
* Alice 選擇：看漲
* 投注：20 USDT
* 如果到期時 BTC 收漲 → Alice 獲勝，並自動獲得賠付。

#### Ben 的例子

Ben 認為 BTC 會降溫回調。

* Ben 選擇：看跌
* 投注：20 USDT
* 如果 BTC 收跌（或符合該市場確切的平局規則）→ Ben 獲勝。

{% hint style="info" %}
有些市場把“持平”算作看跌，有些則將其視為退款。以市場的**規則**部分為最終結算依據。
{% endhint %}

***

### 0Y 如何結算市場

0Y 按照市場列出的結算方式確定結果，通常包括：

* Binance 實時行情 API
* Chainlink 數據流
* 必要時使用其他第三方來源

結算依據：

* 市場規則中定義的確切時間點 / 時間窗口
* 市場定義的標的（例如 BTC/USDT 現貨與永續合約——必須明確說明）

#### 數據不明確時：退款政策

如果因數據質量問題（結算數據缺失、不一致或不可靠）出現爭議，0Y 會：

> ✅ 向該市場的所有交易者退款。

這樣做是為了在外部數據出問題時保護用戶並維護信任。


---

# 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/ru-men-zhi-nan/how-you-can-profit.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.