> 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-tw/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-tw/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.