> For the complete documentation index, see [llms.txt](https://docs.darkbet.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darkbet.fun/wei-shen-me-xuan-ze-darkbet.md).

# 为什么选择 Darkbet？

预测市场有效，但当它们变得过于公开时会崩溃。公开的订单簿暴露了意图。交易者开始相互反应，而不是对信息作出反应。流动性追随关注度而非准确性。本应成为知识竞争的游戏常常变成信号传递的游戏。

#### 核心问题

当每个仓位都是公开的，市场就会失去平衡。一次大型下注可能改变赔率，不是因为有新信息，而是因为所有人都看到了并做出反应。抢先交易和操纵变得有利可图。链上市场更直接地面临这一问题，因为每个仓位和交易都能实时可见，规模较小的市场受到的冲击最大。

#### DarkBet 方法

DarkBet 正在构建以解决此问题。该协议引入了 **暗池市场**，在这些市场中仓位和流动性在结算前保持加密。\
每个市场都被设计为通过智能合约私密运行，只有在验证后才披露最终结果。 

#### 预言机层

我们正在设计一个 **混合预言机网络** ，将由 AI 驱动的数据代理与乐观和密码学验证结合（受 UMA 协议启发）。当来源一致时，市场可以即时结算。来源不一致时，代理会评估可信度并达成可验证的结果。目标是创建一个既快速、去中心化且无人工偏见的结算过程。

#### 隐私基础

我们的隐私层正在围绕一种 **加密 ERC-20（eERC20）** 标准开发。它使用 zk-SNARKs 和部分同态加密来在链上证明正确性的同时保持余额和交易金额的私密性。\
所有加密和证明生成将在用户设备本地进行，确保用户完全控制其密钥和数据。

#### 这将实现的功能

完成后，Darkbet 将允许真实的价格发现而不受可见性偏差的影响。任何规模的交易者都将基于信息而非影响力竞争。\
关于治理、选举或宏观事件的市场将能够在不被群体扭曲的情况下发展。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.darkbet.fun/wei-shen-me-xuan-ze-darkbet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.