Perp DEX volume share, live 24h notional ranked
TradingAevo
Trails$5.33M
- p99
- $8.51M
- rank
- #22
- samples
- 2,880
Nado
Leads$129.33M
- p99
- $290.29M
- rank
- #12
- samples
- 2,880
Aevo leads on 2 of 3 shared benchmarks, Nado on 1. Aevo wins on Most tradable markets on a perp DEX, live count per venue (238 vs 71), Perp DEX volume to open interest (0.240x vs 1.710x). Nado wins on Perp DEX volume share, live 24h notional ranked ($129.33M vs $5.33M). Data as of 2026-10-25 UTC.
OP Stack perp DEX with deep options support, event-driven flow.
Nado is an orderbook perpetuals DEX on Ink, the Kraken-backed L2, with a central limit orderbook and cross-margin. No token has launched yet.
Aevo
Trails$5.33M
Nado
Leads$129.33M
Aevo
Leads238
Nado
Trails71
Aevo
Leads0.240x
Nado
Trails1.710x
The ratio is a screen, not a verdict. Both terms are the venue's own figures (24h volume and open interest as each API reports them, in USD), so a venue that counts both legs of a fill moves its ratio without changing anything real. A very low ratio (Ostium, 0.2x) means positions held for days on thin daily volume; a very high one (Kalshi, above 40x) means a day of trading dwarfs what stays open. The bands in the methodology say what each range usually means.
Aevo and Nado are compared on 3 shared OpenChainBench benchmarks. Aevo leads on Most tradable markets on a perp DEX, live count per venue. Nado leads on Perp DEX volume share, live 24h notional ranked. See the live table on this page for every metric.
On the Most tradable markets on a perp DEX, live count per venue benchmark, Aevo leads at 238 versus Nado at 71. Live measurement is updated continuously by the OpenChainBench harness.
On the Perp DEX volume share, live 24h notional ranked benchmark, Nado leads at $129.33M versus Aevo at $5.33M. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.