Builders and traders constantly ask: CLOB or AMM? The honest answer is conditional. This chapter is a decision guide, not a tribal slogan—with ties to when price is informative and how arbitrage and manipulation economics differ by engine.
One-line comparison
On an order book, price comes from competing limit orders; the design shines with sustained high volume and struggles at cold start without makers. On an AMM, price comes from formula plus pool; it shines with always-on quotes and long tail listing and struggles when depth requires heavy locked capital. Retail UX is simpler on pools; surveillance tooling is richer on centralized books. Neither logo implies honesty—liquidity and resolution do.
| Order book (CLOB) | AMM | |
|---|---|---|
| Quote source | Human or algo limits | Formula + pool |
| Best at | Sustained high volume | Always-on quote, long tail |
| Weak at | Cold start | Capital-heavy depth |
| Manipulation | Needs size at levels | Cheaper on thin pools |
Choose CLOB when…
Regulated U.S.-style event contracts with professional market makers, election and macro headlines with expected millions in notional, participants who need limit orders and cancel/replace, and compliance that wants traditional surveillance fit the CLOB lane. Mature regulated listings and large sports exchanges are the reference case: tight cent-wide spreads and visible depth tables. Your edge is forecasting; execution means not paying the spread twice without reason.
Choose AMM when…
Permissionless listing of many niche questions, crypto-native wallet UX, a credible price day one without maker deals, and play-money or research markets with bounded subsidy fit the pool lane. Early on-chain politics and internal corporate LMSR tools are examples. Module one warned that a number without depth is not a forecast; AMMs always print a number—your job is to judge depth.
Choose hybrid when…
You want retail swap UX and institutional size; the pool seeds price while the book tightens the touch; volume graduates so the book carries the head and the pool carries the tail. Industry arc often runs AMM launch → maker program → book-primary marquee—a sequence, not a winner-take-all verdict.
Trader perspective
Price takers on liquid books fight spread with depth; on liquid pools fight curve slippage; on illiquid either, do not trade size. Market makers quote limits on books or LP into pools with different risk. Arbitrageurs love mismatches between pool and book—their job exists because engines differ.
Worked example: same event, two engines
Hypothetical: “Will Party A control the Senate after November?” A regulated CLOB might show 54¢ / 55¢ with a $3k buy averaging near 55.5¢ all-in. A thin AMM-only venue might display 52% but simulate 57% effective on $3k—the mid lied. A hybrid with active book might fill mostly at 55¢ with pool only if the book gaps—engine choice is execution and credibility, not UX alone.
Compliance and surveillance angle
Regulated books export data to surveillance teams: spoofing, layering, and insider patterns leave fingerprints. Pools also leave on-chain traces, but the interpretive toolkit differs. Builders choosing engines for election markets in the U.S. often start from surveillance requirements, then back into UX—not the reverse. Global crypto venues invert that order and accept different trade-offs.
Size tiers (conceptual)
Small retail tickets ($50–$500) on marquees are usually fine on either engine if depth is real. Mid tickets ($2k–$20k) should default to books or hybrids with simulator checks. Large tickets must read ladders or hybrid priority rules—pool mids are not sufficient. The tier boundaries are not universal; they scale with TVL and maker presence.
Before trading: classify marquee versus long-tail; prefer book or hybrid with visible size on marquees; on long-tail accept simulator effective price and lower media credibility; if your order exceeds a fraction of 24h volume or TVL, you are the market on a pool—on a book, walk the ladder; if two venues disagree more than a few cents after fees, assume arb in flight and verify resolution text matches; apply the informative-price filter—different resolution means stop comparing.
Media and research use
Journalists love a single number; books give two (bid and ask) and researchers must choose. When citing prediction-market odds from a pool, say effective price for a defined notional or mid after last trade and name the venue. When citing a CLOB, cite mid with spread or last trade size. Engine choice shapes how often the public misreads markets—not only how traders execute.
Migration patterns in the wild
Common paths: AMM-only launch → users → CLOB or makers as volume proves; CLOB-only rarely adds AMM except long tail; parallel venues on the same event linked by arb. Research LMSR, regulated books, crypto pools, and hybrid maturity are chapters in one story.
Failure modes
Empty CLOB ladder versus tiny b and huge slippage; news shock widening spread twenty cents versus fifteen percent move on $500 pool flow; spoof walls versus $800 pump; stale mid versus stale formula price; trading halts versus geo-block and oracle pause. Engine picks which failure mode you are fighting.
Builder cheat sheet
Idea stage: LMSR or small AMM with modest b. Product-market fit: raise b or add LPs. Viral event: emergency hybrid or maker program. Mature marquee: CLOB-primary, pool backstop only. When both legs exist on one platform, read which fills first, which mid the tile shows, and whether fees differ by leg—the hybrid chapter details architecture; this chapter’s rule is that the logo does not tell you the engine.
Long-term industry path
No venue needs to stay pure forever. The decision framework is stage-based: launch, prove interest, buy depth, add surveillance. Traders riding that arc should re-check which engine filled them after major product updates—apps change matching priority without changing brand names.
Play-money versus real-money
Research LMSR markets with tiny b teach mechanics but not manipulation economics. Real-money pools attract adversarial flow. Engine choice for a university lab can be LMSR-small-b; engine choice for a presidential contract should not copy that parameter without copying the subsidy budget.
Forecasting teams inside companies
Internal prediction markets sometimes choose LMSR for bounded loss and simple ops, while customer-facing products choose CLOB for credibility. The decision guide is the same: who must trade, how much size, and what happens if the quote is wrong on day one.
Tie-in to aggregation
Informative prices need real aggregation. CLOB aggregates via competing limits when makers are paid to show up. AMM aggregates via formula—always on, but may aggregate only your trade. Comparing percents across venues without volume and rules compares two estimators, not duplicate polls. Manipulation on books often needs sustained size at multiple prices; on thin pools, one-sided curve walks suffice.
Resolution-first reminder
Engine choice is irrelevant if the contract text does not match your forecast target. The decision guide assumes equivalent events; when in doubt, stop at resolution before comparing CLOB and AMM execution.
Summary sentence
Pick the engine that matches event tier, ticket size, and resolution—everything else is marketing.
Key ideas
High-stakes plus makers → CLOB advantage. Long-tail plus crypto UX → AMM advantage. Scale-ups → hybrid. Match venue to trade size, event tier, and resolution—not brand.
When two venues disagree, fix resolution first, then engine, then size—never the brand logo first. The framework is boring on purpose: most costly mistakes are mislabeled liquidity, not wrong forecasts.
Next: how hybrids are architected in production.