GRVT vs Nado

GRVT leads on all 3 live benchmarks. GRVT wins on Perp DEX volume share, live 24h notional ranked ($491.52M vs $224.71M), Most tradable markets on a perp DEX, live count per venue (194 vs 75), Perp DEX volume to open interest (1.029x vs 2.39x). Data as of 2026-09-23 UTC.

Read methodology Last measured Window: rolling 24h3 shared benchmarks
GRVT logo
GRVT

zkSync hybrid CEX/DEX perp venue with privacy-preserving order matching.

Nado logo
Nado

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.

Side by side measurements

Perp DEX volume to open interest: 24h turnover per dollar of OI, live

Trading

GRVT

Leads

1.029x

p99
1.079x
rank
#7
samples
2,853

Nado

Trails

2.39x

p99
4.59x
rank
#13
samples
2,875
Volume / OI (24h)
GRVTn/aNadon/a

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.

Rolling 24h · Volume / OI (24h)Raw JSON

Frequently asked questions

GRVT vs Nado: which one is better?

GRVT and Nado are compared on 3 shared OpenChainBench benchmarks. GRVT leads on Perp DEX volume share, live 24h notional ranked. See the live table on this page for every metric.

Which has the higher 24h perp volume, GRVT or Nado?

On the Perp DEX volume share, live 24h notional ranked benchmark, GRVT leads at $491.52M versus Nado at $224.71M. Live measurement is updated continuously by the OpenChainBench harness.

How is the GRVT vs Nado comparison measured?

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.

How this pair was selected

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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.