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

# Decentralization

The Road to Decentralisation

0Y’s current architecture is deliberately practical: the pricing engine runs off-chain, blockchain records confirmed transactions as proof, and the treasury seeds initial liquidity. This is a conscious design choice, not a limitation.

#### Why Off-Chain Engine Makes Sense Now

* Speed: On-chain LMSR calculations are slow and expensive. Off-chain means instant price updates.
* Flexibility: We can adjust parameters, respond to attacks, and improve the engine without smart contract upgrades.
* Cost: No gas fees on every price update — critical for 1-minute markets with dozens of updates per minute.
* Auditability: Blockchain records every confirmed bet as an immutable receipt, providing the trust layer without the cost.

#### The Path to External Liquidity

0Y’s treasury seeds markets now. The long-term vision has three phases:

| **Phase**                    | **Liquidity Source**                                           | **Status** |
| ---------------------------- | -------------------------------------------------------------- | ---------- |
| Phase 1 — Bootstrap          | Protocol treasury seeds all markets with capped risk parameter | Current    |
| Phase 2 — LP Integration     | External liquidity providers earn fees by seeding markets      | Future     |
| Phase 3 — Market Maker Layer | Professional market makers compete for market seeding rights   | Future     |

LMSR's mathematical properties make this transition smooth. The risk parameter is the dial — increasing it as external liquidity comes in is a configuration change, not an architecture change.

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