based.app vs Sushi

Name: based.app vs Sushi OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

based.app leads on the only live benchmark. based.app wins on Hyperliquid frontends builder revenue leaderboard ($25.5K vs $90.44).

Read methodology Last measured Sat, 22 Aug 2026 02:13:05 UTCWindow: rolling 24h1 shared benchmark

based.app

Based is a Hyperliquid super app combining perps, prediction markets and a Visa card; one of the top builders by perp volume on Hyperliquid, running its own Builder on Builder program.

Sushi

Sushi is a multichain DEX whose Sushi Perps v2 frontend routes orders into the Hyperliquid orderbook via a builder code, layering Sushi points incentives on top.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading

Provider	Builder fees collected	Volume routed	Users 24h	Effective fee bps	Time since last fill
based.app	$25.5K	$106.57M	515	0.024%	20.8 s
Sushiprovisional	$90.44	$150.7K	5	0.060%	25.2 min

Ranking is by raw builder fee revenue in USD, not by value for users. Bigger number means more fees collected via the on-chain builder code field. For the trader cost perspective, switch to the Effective fee bps companion tab. Native Hyperliquid UI orders carry no builder code and are excluded. Data from a local hl node tailing every fill on mainnet.

Frequently asked questions

based.app vs Sushi: which one is better?

based.app and Sushi are compared on 1 shared OpenChainBench benchmarks. based.app leads on Hyperliquid frontends builder revenue leaderboard. See the live table on this page for every metric.

Which is cheaper, based.app or Sushi?

On the Hyperliquid frontends builder revenue leaderboard benchmark, based.app leads at $25.5K versus Sushi at $90.44 (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the based.app vs Sushi 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.