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