Aevo vs GMX

GMX leads on both live benchmarks. GMX wins on Perp DEX volume share, live 24h notional ranked ($117.38M vs $4.06M), Perp DEX daily volume 2026 ($115.35M vs $3.88M). Data as of 2026-11-21 UTC.

Read methodology Last measured Window: rolling 24h3 shared benchmarks, 2 measured on both sides
Aevo logo
Aevo

OP Stack perp DEX with deep options support, event-driven flow.

GMX logo
GMX

Perp DEX on Arbitrum and Avalanche. Pool-based execution against GLP and GM vaults, oracle-priced trades with no orderbook.

Daily perp volume, head to head

Perpetual notional per closed UTC day, the DeFiLlama day buckets, read from each venue's own data. Ribbon under the bars marks which venue printed more that day.

Bench 266, all venues

7d lead

GMX

$32.7M vs $555M

30d lead

GMX

$126M vs $2.04B

Days led, last 30

0 / 30

Aevo / GMX

Current streak

90 days

GMX since Aug 23, 2026

AevoGMX

UTC days, one side per trade

050M100M150M200MAug 23Nov 20lead

Aevo volume ÷ GMX volume, week by week

The ratio of the two venues' seven-day perp volume, in percent; a window is shown only when both sides have every day closed. 100% is parity. The dashed line is the median of the weeks shown; the last window is the 7d tile above.

5.9% · week to 20 Nov · median 6.0%

Aevo ÷ GMX, seven-day windows ending on the last closed day

0%50%100%median 6%7 Aug21 Aug4 Sep18 Sep2 Oct16 Oct30 Oct13 Nov20 Nov

14 Nov to 20 Nov

Aevo ÷ GMX5.9%
vs median-0.2pt
= Aevo volume$32.7M
÷ GMX volume$555.2M
WindowAevoGMXAevo / GMX
Last closed day (Nov 20, 2026)$3.9M$115M3%
Last 7 days$32.7M$555M6%
Last 30 days$126M$2.04B6%

Sources: Aevo, Aevo /statistics PERPETUAL daily_volume per UTC day. GMX, GMX V2 synthetics squids, marginVolumeUsd (perps only, swaps excluded), Arbitrum + Avalanche + Botanix + MegaETH. Days where either venue has not closed are left blank rather than counted as zero. Last closed day common to both: Nov 20, 2026. Methodology and every venue on bench 266.

Side by side measurements

Perp DEX daily volume 2026: Hyperliquid, Aster, Lighter, GMX, Gains, dYdX by UTC day, backfilled

Trading
ProviderDaily perp volumeVolume 30dShare 30d
Aevo$3.88M$125.54M0.028%
GMX$115.35M$2.04B0.45%
View
Aevon/aGMXn/a

Volume is self-reported by each venue's public data surface and counted per UTC day, one side of each trade. Perimeters differ slightly per venue and are stated in the ledger notes. A closed day can be restated by a venue for one to two days; the harness re-reads the last three days every hour. Not a measure of organic flow: incentive programs and wash trading inflate notional on every venue.

Last closed day · Daily perp volumeRaw JSON

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

Trading

Aevo

Trails

0.249x

p99
0.367x
rank
#3
samples
2,880

GMX

No data in window

Volume / OI (24h)
Aevon/aGMXn/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

Aevo vs GMX: which one is better?

Aevo and GMX are compared on 3 shared OpenChainBench benchmarks. GMX 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, Aevo or GMX?

On the Perp DEX volume share, live 24h notional ranked benchmark, GMX leads at $117.38M versus Aevo at $4.06M. Live measurement is updated continuously by the OpenChainBench harness.

How is the Aevo vs GMX 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.

Related comparisons

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.