> 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/tracking-your-positions.md).

# 追踪你的持仓

#### 在哪里查看持仓

前往：

* “我的持仓”（或仪表盘），查看所有未结算和已结算的交易。

你通常会看到：

* 市场名称
* 选择的方向
* 投注金额
* 到期时间
* 状态（进行中 / 已结算 / 已退款）
* 结算后的赔付结果

{% hint style="info" %}
如果你的持仓很多，可以先筛选“进行中”，以免错过即将到期的市场。
{% endhint %}

***

#### Alice 的习惯

Alice 每天查看一次“我的持仓”：

* 进行中 → 看看哪些仓位仍然有效
* 已结算 → 回顾哪些判断是对的
* 已退款 → 了解少见的数据质量问题


---

# 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/tracking-your-positions.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.