Arena vs Pear

Name: Arena vs Pear OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

Pear leads on the only live benchmark. Pear wins on Hyperliquid frontends builder revenue leaderboard ($1,180.89 vs $51.09).

Read methodology Last measured Thu, 27 Aug 2026 04:04:05 UTCWindow: rolling 24h1 shared benchmark

Arena

The Arena is an Avalanche based SocialFi app whose Arena perps feature routes orders to Hyperliquid and exposes copy trading of those positions, using a registered builder code.

Pear

DeFi native pair trading terminal enabling one click long short ratio trades on top of Hyperliquid, GMX, and SYMMIO.

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
Arenaprovisional	$51.09	$56.2K	12	0.091%	9.4 min
Pear	$1,180.89	$1.97M	54	0.060%	4.9 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

Arena vs Pear: which one is better?

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

Which is cheaper, Arena or Pear?

On the Hyperliquid frontends builder revenue leaderboard benchmark, Pear leads at $1,180.89 versus Arena at $51.09 (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the Arena vs Pear 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.