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