AVNT vs DRV

Name: AVNT vs DRV OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

AVNT leads on the only live benchmark. AVNT wins on Perp DEX price to fees ratio 2026 (12.2x vs 18.6x).

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

AVNT

Avantis is a synthetic perpetuals DEX on Base covering crypto, forex and commodities. Trades settle against a USDC vault with oracle pricing; AVNT is the protocol token.

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.

Side by side measurements

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

Trading

Provider	P/F ratio	FDV / fees	Fees 30d	Float	Open interest	Fees / OI
AVNT	12.2x	34.5x	$229.3K	35.3%	$14.31M	0.195x
DRV	18.6x	27.7x	$619.0K	66.6%	$56.09M	0.134x

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

AVNT vs DRV: which one is better?

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

Which is faster, AVNT or DRV?

On the Perp DEX price to fees ratio 2026 benchmark, AVNT leads at 12.2x versus DRV at 18.6x. Live measurement is updated continuously by the OpenChainBench harness.

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