edgeX vs Kalshi

Split decision: edgeX leads on Most tradable markets on a perp DEX, live count per venue (176 vs 21) and Perp DEX volume to open interest (2.63x vs 40.5x); Kalshi leads on Cheapest perp venue to hold a position, live funding normalized (2.03 bps vs 3.00 bps) and Funding paid to hold an ETH perp long for 30 days, per venue, live (62.7 bps vs 90.0 bps). Data as of 2026-09-23 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.

Kalshi logo
Kalshi

CFTC-regulated US prediction market exchange. REST trade API (trade-api/v2) with documented per-tier rate limits; the market data WebSocket requires authentication.

Side by side measurements

Cheapest perp venue to hold a position, live funding normalized

Trading

edgeX

Trails

3.00 bps

p99
3.00 bps
rank
#13
samples
1,506

Kalshi

Leads

2.03 bps

p99
0 bps
rank
#5
samples
2,876
Funding cost to hold a long 24h
edgeXn/aKalshin/a

Funding is signed. Positive means longs pay shorts, negative means longs get paid to hold. Venues settle on different native periods (hourly on Hyperliquid, dYdX, Lighter, Extended, Pacifica, Ondo, Vest, StandX and ApeX, every 4h on edgeX, every 8h on Kalshi, Aster and the CEX books); every figure is normalized from the venue's own quoted rate and interval before ranking. Funding is only the holding cost. Opening costs (taker fee, spread, impact) are the companion bench perp-fees.

Rolling 24h · Funding cost to hold a long 24hRaw JSON

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

Trading

edgeX

Leads

2.63x

p99
2.93x
rank
#15
samples
2,797

Kalshi

Trails

40.5x

p99
43.6x
rank
#22
samples
2,876
Volume / OI (24h)
edgeXn/aKalshin/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

Funding paid to hold an ETH perp long for 30 days, per venue, live

Trading

edgeX

Trails

90.0 bps

rank
samples
11provisional

Kalshi

Leads

62.7 bps

rank
samples
29provisional
Funding paid, 30d ETH long
edgeXn/aKalshin/a

Every row is a month of funding at the venue's average daily cost over the hours measured in the trailing 30 days (average x 30). A venue ranks only with 576 of the 720 hours (24 days) behind that average; under the floor the row is provisional, unranked, and shows its day count (the venues added on 2026-09-22 and 2026-09-23 start there). Funding is signed: on a month where shorts paid longs the figure is negative and "cheapest" means "was paid the most".

Rolling 24h · Funding paid, 30d ETH longRaw JSON

Frequently asked questions

edgeX vs Kalshi: which one is better?

edgeX and Kalshi are compared on 4 shared OpenChainBench benchmarks. edgeX leads on Most tradable markets on a perp DEX, live count per venue. Kalshi leads on Cheapest perp venue to hold a position, live funding normalized. See the live table on this page for every metric.

Which has the higher active markets, edgeX or Kalshi?

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

Which is cheaper, edgeX or Kalshi?

On the Cheapest perp venue to hold a position, live funding normalized benchmark, Kalshi leads at 2.03 bps versus edgeX at 3.00 bps. Live measurement is updated continuously by the OpenChainBench harness.

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