DRV vs DRIFT

DRV vs DRIFT on 2 shared OpenChainBench benchmarks, awaiting live measurements.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
DRV logo
DRV

Derive (formerly Lyra) is an options and perpetuals exchange on its own OP Stack rollup with an off-chain orderbook and on-chain settlement. DRV is the protocol token.

DRIFT logo
DRIFT

Solana perp DEX with hybrid AMM/orderbook model, sub-second matching via Anchor program.

Side by side measurements

Perp DEX token P/E ratio 2026: Hyperliquid, Lighter, GMX, dYdX, GNS live

Trading

DRV

Trails

34.3x

rank
#6
samples
34provisional

DRIFT

No data in window

P/E = fully diluted valuation (CoinGecko) divided by annualized protocol revenue (DeFiLlama dailyRevenue, 30-day trailing average x365). Protocol revenue = fees accruing to the treasury or token holders, not total user fees. Tokens without a CoinGecko listing show no P/E. FDV reflects total supply at current price, not circulating supply; tokens with large unvested allocations will show inflated FDV-based P/E. Updated hourly.

Perp DEX price to fees ratio 2026: Hyperliquid, Aster, Lighter, GMX, GNS live

Trading
ProviderFees 30dFloat
DRV$619.0K66.6%
DRIFT-71.5%

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

DRV vs DRIFT: which one is better?

DRV and DRIFT are compared on 2 shared OpenChainBench benchmarks. See the live table on this page for every metric.

How is the DRV vs DRIFT 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.

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.