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