> 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/ru-men-zhi-nan/what-is-0y-markets.md).

# 什么是 0Y Markets？

0Y Markets 是东南亚第一个预测市场

{% hint style="warning" %}
待补充截图（0Y 应用）。
{% endhint %}

### 快速概览

在 0Y Markets 上：

* 你可以交易各种结果，例如：
  * “未来 15 分钟内 BTC 收盘会看涨还是看跌？”
  * “A 队今晚会赢吗？”
  * “事件 X 会在 Y 日期之前正式宣布吗？”
* 你可以在多个网络上充值支持的稳定币：
  * **USDT 和 USDC**：BNB Chain、Arbitrum、Polygon、Ethereum、Solana 等
  * **USDC**：Base 和 Arc
  * **USDG**：Robinhood Chain
  * 也可以通过 **Binance Connect** 充值
* 0Y 使用 **LMSR（对数市场评分规则）**，而不是点对点订单簿：
  * 交易按当前报价立即成交
  * 不需要其他用户来撮合你的交易
* 市场结算时，0Y 使用市场规则中指定的数据来源，可能包括：
  * Binance 实时行情 API
  * Bybit WebSocket 数据流
  * Chainlink 数据流
  * 视市场而定的其他第三方数据提供商

如果某个市场因数据质量问题无法可靠结算，0Y 可能会将该市场标记为**已退款/无效**，并退还投入该市场仓位的金额。

{% hint style="success" %}
如果某个市场出现数据质量争议，0Y 会向该市场的所有交易者全额退款。
{% endhint %}

***

### 为什么大家使用 0Y Markets

大家使用 0Y Markets 来：

* 在 **1 分钟、5 分钟和 15 分钟市场**中交易快速变化的加密货币行情
* 交易**体育、金融、文化、加密货币、大宗商品**等领域的真实事件
* 无需复杂的交易工具就能表达自己的观点
* 确认交易之前就能看到潜在赔付
* 在规则清晰、结算标准透明的市场中交易
* 即使没有 DeFi 或预测市场经验也能参与

如果你擅长看图表、追踪新闻、理解趋势或捕捉情绪变化，0Y Markets 让你可以简单地就你认为接下来会发生的事情进行交易。


---

# 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/ru-men-zhi-nan/what-is-0y-markets.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.
