> 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/jiao-yi/odds-change.md).

# 賠率變化

### 為什麼我點擊確認之前賠率變了？

賠率可能會快速變化，原因包括：

* BTC 價格變動
* 波動率上升
* 距離到期的時間縮短
* 其他用戶在你確認之前完成了交易

如果賠率發生變化，你會看到更新後的賠付預覽。

{% hint style="info" %}
如果賠率變了，而你不再滿意新的賠付，不確認就好。在你確認之前，什麼都不會生效。
{% endhint %}

***

#### Charlie 的例子

Charlie 正準備點擊看漲，但 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/jiao-yi/odds-change.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.