Azuro

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Azuro pools stablecoin liquidity as the counterparty to thousands of prediction markets, allocating capacity through its LiquidityTree and booking maximum potential losses as Reinforcement. This is event-outcome underwriting, not paired-token impermanent loss, and no existing higher-order dossier directly disposes of it. Capacity therefore decides: the 2026-08-15 survey reported approximately $1.59M across six chains, far below the version-1 below-materiality threshold.

Kill criteria: the events that revoke this verdict
• TVL sustained above $100M for 30 days

The research file

Mechanism applicability

An Azuro LP deposit enters a singleton stablecoin pool that services many concurrent prediction markets. Data Providers set sell-side odds and each market books pool capacity through Reinforcement and Virtual Funds; resolved bettor outcomes return a profit or loss to the pool. The claim is neither a paired AMM position nor ordinary lending: the LP earns an odds spread while underwriting bettors across changing event markets.

Current observation and perimeter

The DefiLlama protocol API read on 2026-08-15 classified Azuro as a Prediction Market and reported approximately $1.59M across Polygon, Base, Arbitrum, Linea, Gnosis and Chiliz, expanding the stale two-chain registry perimeter. Current documentation includes June and July 2026 toolkit releases and the current v3 LiquidityTree, supporting an active rather than archived lifecycle.

Control, loss and exit applicability

Permissioned Data Providers currently choose and reprice sell-side odds, may pause markets and initially define each Condition’s maximum-loss Reinforcement; AzuroDAO resolves disputes as arbiter of last resort. Deposits absorb profit and loss across every supported market, including negative returns when bettors outperform. LPs face an initial seven-day lock and may withdraw afterward, but lazy LiquidityTree accounting first realizes unresolved-condition P&L into the leaf balance.

Why the class rule decides

Azuro expressly distinguishes its underwriting pool from impermanent-loss AMMs, so forcing the amm-lp dossier would misstate the loss path. No other current dossier specifically covers diversified prediction-market underwriting. At roughly $1.59M, however, one advised practice could dominate total capacity before odds controls, event resolution, chain distribution or proposed-size exits are reviewed. Reopen after TVL remains above $100M for 30 days, then perform an individual underwriting review.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Azuro — current protocol documentation and releases · primary · accessed 2026-08-15
  Supports: prediction markets, current releases, singleton LP, data providers, event resolution
• Azuro — LP mechanism, returns and withdrawal terms · primary · accessed 2026-08-15
  Supports: all-market exposure, bettor outperformance, seven-day lock, withdrawal, LP profit and loss
• Azuro — LiquidityTree accounting and exit · primary · accessed 2026-08-15
  Supports: singleton pool, profit and loss attribution, lazy accounting, withdrawal, virtual funds
• Azuro — maximum-loss Reinforcement · primary · accessed 2026-08-15
  Supports: initial liquidity, prediction outcomes, maximum potential loss, condition creation
• Azuro — Data Provider controls and LP protection · primary · accessed 2026-08-15
  Supports: not impermanent loss, odds control, market pause, permissioned data providers, loss collateral
• DefiLlama — Azuro survey record · secondary · accessed 2026-08-15
  Supports: current TVL, current chains, Prediction Market category, survey observation

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.