edgeX vs Jupiter Perps

edgeX leads on all 4 live benchmarks. edgeX wins on Most tradable markets on a perp DEX, live count per venue (178 vs 3), Perp DEX price to fees (2.84x vs 5.50x), Perp DEX volume to open interest (0.838x vs 0.986x), Price to fees across DeFi (2.88x vs 5.51x). Data as of 2026-10-11 UTC.

Read methodology Last measured Window: rolling 24h4 shared benchmarks
edgeX logo
edgeX

StarkEx-settled perp DEX with low taker fees and a documented public REST API.

Jupiter Perps logo
Jupiter Perps

Solana swap aggregator. REST APIs for quotes, swap routing, price, and token lists across Solana DEXs.

Side by side measurements

Perp DEX price to fees: what the market pays per dollar of trading fees

Trading
ProviderP/F ratioFDV / feesP/SFees 30dRevenue 30dFloatOpen interestFees / OI
edgeX2.84x8.15x3.94x$3.65M$2.64M35.0%$218.39M0.203x
Jupiter Perps5.50x11.4x16.9x$17.75M$5.77M48.4%$42.47M5.09x
View
edgeXn/aJupiter Perpsn/a

P/F = circulating market cap (CoinGecko) / annualized fees (DeFiLlama dailyFees, trailing 30d x 365/30), on the DeFiLlama parent the token accrues from. Fees include the share paid to liquidity providers; P/S uses protocol revenue only. Low-float tokens show a much higher FDV/F than P/F. Pre-TGE venues are listed unranked with fees and OI, no ratio. A low multiple is not a recommendation.

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

Trading

edgeX

Leads

0.838x

p99
1.293x
rank
#11
samples
2,880

Jupiter Perps

Trails

0.986x

p99
1.381x
rank
#13
samples
2,880
Volume / OI (24h)
edgeXn/aJupiter Perpsn/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

Price to fees across DeFi: what the market pays per dollar of protocol fees

Trading
ProviderP/F ratiovs categoryFees MoMToken 30dFloatFDV / feesMarket capFees 30dRevenue 30dP/STVLSupply 30dSupply 90d
edgeX2.88x0.351x--35.0%8.17x$126.83M$3.65M$2.64M4.72x$60.47M--
Jupiter Perps5.51x0.669x-57.1%48.4%11.3x$1.19B$17.94M$5.80M16.8x$2.56B--
View
edgeXn/aJupiter Perpsn/a

A screen, not a verdict, and not advice. P/F = circulating market cap (CoinGecko) / annualized fees (DeFiLlama, trailing 30d x 365/30) summed across every fee adapter that accrues to the token. Fees include the share paid to liquidity providers. A low multiple can mean the market expects fees to fall, that the fees were incentivised, or that the token has no claim on them. Read it with the float, the category median and the monthly fee trend, then do your own work.

Frequently asked questions

edgeX vs Jupiter Perps: which one is better?

edgeX and Jupiter Perps are compared on 4 shared OpenChainBench benchmarks. edgeX leads on Most tradable markets on a perp DEX, live count per venue. See the live table on this page for every metric.

Which has the higher active markets, edgeX or Jupiter Perps?

On the Most tradable markets on a perp DEX, live count per venue benchmark, edgeX leads at 178 versus Jupiter Perps at 3. Live measurement is updated continuously by the OpenChainBench harness.

How is the edgeX vs Jupiter Perps 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.