Most tradable markets on a perp DEX, live count across 14 venues
TradingdYdX
Trails78
- p99
- 78
- rank
- #10
- samples
- 2,880
Ostium
Leads83
- p99
- 83
- rank
- #9
- samples
- 2,880
Ostium leads on both live benchmarks. Ostium wins on Most tradable markets on a perp DEX, live count across 14 venues (83 vs 78), Perp DEX capital efficiency (7 vs 0.718).
Perp DEX on the dYdX Chain, a Cosmos SDK appchain. Orderbook with off-chain matching and onchain settlement, validators propagate orders via the mempool.
Arbitrum-based perp DEX specialized in RWA exposure including FX, commodities and indices.
dYdX
Trails78
Ostium
Leads83
dYdX
Trails0.718
Ostium
Leads7
TVL from DefiLlama /protocol/{slug} currentChainTvls, excluding staking and pool2 categories. Market count from each venue's native API (same source as the perp-active-markets bench). The ratio reflects architectural choices, not absolute liquidity: a high ratio means the venue can list many markets cheaply, not that each market has deep liquidity. Compare with perp-open-interest for the liquidity angle.
| Provider | Fees 30d | Revenue 30d | Open interest | Fees / OI |
|---|---|---|---|---|
| dYdX | $288.7K | $288.7K | $53.19M | 0.066x |
| Ostium | $765.8K | $543.8K | $7.89M | 1.180x |
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.
dYdX and Ostium are compared on 3 shared OpenChainBench benchmarks. Ostium leads on Most tradable markets on a perp DEX, live count across 14 venues. See the live table on this page for every metric.
On the Most tradable markets on a perp DEX, live count across 14 venues benchmark, Ostium leads at 83 versus dYdX at 78. Live measurement is updated continuously by the OpenChainBench harness.
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.
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.