> 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-odds-calculated.md).

# 赔率如何计算

在 0Y Markets 上，你看到的赔率是 0Y 对每一边（YES/NO 或看涨/看跌）的实时报价。0Y 的预测市场平台使用 LMSR 定价引擎。

0Y 会根据以下因素实时更新赔率：

* 标的市场的走势（例如 BTC 价格和波动率）
* 距离到期的剩余时间
* 风险限额和敞口平衡（以保持市场稳定、可持续）

{% hint style="info" %}
赔率越高通常意味着潜在赔付越高，但也说明该结果在当下被认为可能性较低。
{% endhint %}

***

#### “赔率”在 0Y Markets 上的含义

可以把赔率理解为：“如果我投入 X，判断正确时能拿回多少？”

你始终会看到：

* 你的投注金额
* 你选择的一边
* 获胜时的预估赔付（在你确认之前）

***

#### 示例：Alice 交易 BTC 15 分钟收盘

市场：“BTC 15 分钟收盘：看涨还是看跌？”

* Alice 选择看涨
* 投入 20 USDT
* 0Y 显示赔付预览（示例）：“获胜赔付：36 USDT”
* Alice 确认

如果到期时 BTC 收涨 → 她获胜，赔付计入账户。


---

# 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-odds-calculated.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.