> 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/chang-jian-wen-ti/markets-and-trading-basics.md).

# 市场与交易基础

#### 0Y 提供哪些类型的市场？

常见类型包括：

* 加密货币时间窗口市场（例如 BTC 15 分钟收盘看涨/看跌）
* 另类加密指数（例如恐惧与贪婪指数）
* 加密衍生品类产品（例如流动性热力图）
* 现实世界资产合约（例如黄金、白银、原油）
* 新闻/事件市场（由指定来源核实）
* 创新产品（面向 Meme 代币的战壕市场）

#### 如何完成第一笔交易？

1. 充值 USDT/USDC/USDG，请参阅[如何充值](/zh/chong-zhi-yu-ti-xian/how-to-deposit.md)
2. 选择一个市场
3. 选择 YES/NO 或看涨/看跌
4. 输入投注金额
5. 查看赔付预览
6. 确认

#### 为什么我的交易能立即成交？

因为 0Y 是使用 LMSR 的平台（而不是 P2P）。你接受的是 0Y 基于 LMSR 定价引擎给出的报价赔率，而不是等待另一位用户。

#### BTC 15 分钟市场中的“看涨/看跌”是什么意思？

意思是把 BTC 到期时的收盘价与市场规则中定义的参考价进行比较。持平时的具体处理方式写在规则中。

#### 如果 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/chang-jian-wen-ti/markets-and-trading-basics.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.