> For the complete documentation index, see [llms.txt](https://whitepaper.after-bell.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.after-bell.uk/trading-architecture/why-clob-not-amm.md).

# Why CLOB, Not AMM

Explains the rationale for order-book trading rather than an automated market maker.

AFTERBELL starts with a CLOB because binary prediction markets have a one-sided terminal outcome. That creates a different liquidity structure from an ordinary two-sided spot market.

### The binary constraint

For “Will NVDA close above $150 on Friday?”:

```
If Yes wins: Yes = $1.00, No = $0.00
If No wins:  No = $1.00, Yes = $0.00
```

The source argues that this final state is unfavorable for AMM liquidity providers. One side necessarily becomes worthless. AFTERBELL therefore does not begin with a traditional AMM pool for core matching.

| Dimension               | AMM                  | AFTERBELL CLOB             |
| ----------------------- | -------------------- | -------------------------- |
| Liquidity model         | Pool-based           | Order-based                |
| Counterparty            | Pool                 | Another order              |
| Matching                | Curve-based pricing  | Order matching             |
| Binary terminal outcome | Creates LP-side risk | Directly matched positions |
| Core matching           | Traditional LP pool  | No traditional LP pool     |

An order book lets buyers and sellers state prices for Yes or No, then matches compatible orders before smart-contract settlement. This does not eliminate liquidity risk. It makes available bids and asks a direct market requirement.

The source references Polymarket’s move from AMM mechanics to CLOB architecture in 2024, alongside approximately $25.7B monthly volume. That is contextual comparison only. It is not a claim about AFTERBELL’s volume, adoption, or future success.


---

# 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://whitepaper.after-bell.uk/trading-architecture/why-clob-not-amm.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.