edgeX vs JUP

Name: edgeX vs JUP OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

JUP leads on the only live benchmark. JUP wins on Perp DEX price to fees ratio 2026 (2.97x vs 3.33x).

Read methodology Last measured Tue, 15 Sep 2026 19:24:47 UTCWindow: rolling 24h1 shared benchmark

edgeX

zkSync-based perp DEX with low taker fees and a documented public REST API.

JUP

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 ratio 2026: Hyperliquid, Aster, Lighter, GMX, GNS live

Trading

Provider	P/F ratio	FDV / fees	P/S	Fees 30d	Revenue 30d	Float	Open interest	Fees / OI
edgeX	3.33x	9.51x	4.61x	$4.95M	$3.57M	35.0%	$585.72M	0.103x
JUP	2.97x	6.15x	8.36x	$20.51M	$7.30M	48.4%	$33.49M	7.45x

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.

Frequently asked questions

edgeX vs JUP: which one is better?

edgeX and JUP are compared on 1 shared OpenChainBench benchmarks. JUP leads on Perp DEX price to fees ratio 2026. See the live table on this page for every metric.

Which is faster, edgeX or JUP?

On the Perp DEX price to fees ratio 2026 benchmark, JUP leads at 2.97x versus edgeX at 3.33x. Live measurement is updated continuously by the OpenChainBench harness.

How is the edgeX vs JUP 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

Jupiter vs Mobula

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.