> 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/shi-chang/what-is-0ys-lmsr/decentralization.md).

# 去中心化

通往去中心化之路

0Y 当前的架构是刻意务实的：定价引擎在链下运行，区块链记录已确认的交易作为凭证，资金库负责注入初始流动性。这是有意为之的设计选择，而不是能力上的限制。

#### 为什么现阶段采用链下引擎

* 速度：在链上进行 LMSR 计算既慢又贵。链下意味着价格可以即时更新。
* 灵活性：我们可以调整参数、应对攻击、改进引擎，而无需升级智能合约。
* 成本：每次价格更新都不需要支付 Gas 费——这对每分钟有几十次更新的 1 分钟市场至关重要。
* 可审计性：区块链把每一笔已确认的下注记录为不可篡改的凭证，以更低成本提供信任保障。

#### 引入外部流动性的路径

目前由 0Y 的资金库为市场注入流动性。长期愿景分为三个阶段：

| **阶段**      | **流动性来源**                 | **状态** |
| ----------- | ------------------------- | ------ |
| 第一阶段——启动期   | 协议资金库为所有市场注入流动性，并设定风险参数上限 | 当前     |
| 第二阶段——LP 集成 | 外部流动性提供者通过为市场注资赚取手续费      | 未来     |
| 第三阶段——做市商层  | 专业做市商竞争市场注资权              | 未来     |

LMSR 的数学特性让这一过渡非常平滑。风险参数就是调节旋钮——随着外部流动性进入而调高它，只是一次配置变更，而不是架构变更。

<br>


---

# 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/shi-chang/what-is-0ys-lmsr/decentralization.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.