CCXT vs Rabby

Name: CCXT vs Rabby OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

Rabby leads on the only live benchmark. Rabby wins on Hyperliquid frontends builder revenue leaderboard ($26.1K vs $200.37).

Read methodology Last measured Fri, 21 Aug 2026 23:03:06 UTCWindow: rolling 24h1 shared benchmark

CCXT

CCXT is the open source multi exchange trading library. Its Hyperliquid integration attaches the CCXT builder code to orders by default, making it one of the largest programmatic flow routers on HL.

Rabby

Open source EVM browser wallet with built in Rabby Perps powered by Hyperliquid for in wallet perpetual futures trading.

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
CCXT	$200.37	$2.02M	82	0.0099%	19.5 s
Rabby	$26.1K	$130.29M	1,369	0.020%	17.6 s

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

CCXT vs Rabby: which one is better?

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

Which is cheaper, CCXT or Rabby?

On the Hyperliquid frontends builder revenue leaderboard benchmark, Rabby leads at $26.1K versus CCXT at $200.37. Live measurement is updated continuously by the OpenChainBench harness.

How is the CCXT vs Rabby 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.