Hyperliquid frontends builder revenue leaderboard
How much USD builder fee revenue each Hyperliquid frontend collected over the rolling 24h, 7 day and 30 day windows. Data from a local hl node tailing every fill on mainnet.
Read this carefully
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.
This page answers one question. Which Hyperliquid frontend collected the most builder fee revenue in USD over the last 24 hours, 7 days and 30 days. Every Hyperliquid order can attach an optional on chain builder field. Frontends like Phantom Perps, MetaMask, Rabby, Insilico, based dot app, OneKey, Axiom and pvp dot trade write their wallet address into this field on every fill they route, then collect a share of the taker fee as their own rebate (capped at 100 basis points on perps, 1000 on spot). The bench ranks 104 frontends by the dollar amount each one collected through this mechanism, surfacing the real revenue scale of the Hyperliquid frontend ecosystem rather than a percentage ratio that hides the actual numbers. Data comes from a local hl node operated on OCB infrastructure tailing the Hyperliquid mainnet fill stream. A Go harness reads every block of attributed fills, aggregates per builder over rolling 24h, 7 day and 30 day windows in memory, and exposes Prometheus gauges that this page consumes. End to end staleness from fill landing on chain to page render is typically under one minute. Companion tabs surface volume routed, unique users, the trader perspective effective fee in basis points, and an outage detector.
Methodology
The bench ranks 104 Hyperliquid frontends by the USD value of builder fees they collected over rolling 24 hour, 7 day and 30 day windows. Source data is a local hl node operated on OCB infrastructure that writes every block of fills to disk as one JSON line. A Go harness tails these files, decodes each fill, and increments per builder hourly buckets keyed by the UTC hour floor of the fill timestamp. At publish time, the harness sums the recent 24, 168 and 720 hourly buckets to compute the 24h, 7d and 30d revenue figures, exposes them as Prometheus gauges (hl_frontend_fees_usd_24h_v2, _7d_v2, _30d_v2), and this page reads the gauges every 30 seconds. The registry of tracked builder addresses lives at miniapps hyperliquid frontends local builders dot json in the open mobula api repo, currently 104 entries seeded from DefiLlama dimension adapters plus a behavioral cross reference pass on the top unidentified addresses. New builders ship via public PR. The bench does not place trades, does not touch private keys, and does not depend on any internal Mobula service.
Frequently asked
What does this benchmark measure?
The USD value of builder fees each Hyperliquid frontend collected over rolling 24 hour, 7 day and 30 day windows. A builder fee is the optional rebate the frontend writes into the builder field on every Hyperliquid order it routes. The on chain protocol caps this at 100 basis points on perps and 1000 on spot. The bench sums every fill's builderFee value attributed to a known frontend address and publishes the total per timeframe.
Why USD revenue instead of effective fee in basis points?
The previous version of this bench ranked frontends by effective fee in basis points, which answered the trader question of cost per dollar routed. The dollar revenue framing answers the operator question of size and revenue scale, the same way CoinMarketMan and ASXN dashboards present builder leaderboards. Both views are useful. The effective fee bps view is still available as a companion tab.
Where does the data come from?
A local hl node operated on OCB infrastructure tails the Hyperliquid mainnet. The node writes every block of fills to disk as one JSON line under node_fills_by_block hourly YYYYMMDD HH. A Go harness running on the same host reads these files continuously, parses each fill, and increments per builder hourly aggregates. No third party API, no daily CSV bucket dependency, no internal Mobula service. Source code is in miniapps hyperliquid frontends local in the open mobula api repo.
How are the 7 day and 30 day numbers built?
The harness keeps a small in memory map of per builder hourly buckets going back 30 days. Each bucket stores the sum of builderFee values and the sum of notional values for fills that landed in that hour. The 7 day figure is the sum of the recent 168 buckets, the 30 day figure is the sum of the recent 720 buckets. Memory footprint is about 350 KB total for all 104 tracked frontends. Buckets older than 30 days are dropped on every publish.
How is the 24 hour figure built?
Same hourly bucket logic, last 24 buckets. The harness also keeps a separate fill level window for the 24h companions that require per fill granularity (unique users, taker share, slippage proxy).
Which frontends are tracked?
Sixty Hyperliquid frontends with a known builder address. The cohort spans consumer wallets (Phantom Perps, MetaMask, Rabby, OneKey, Trust Wallet), pro terminals (Insilico, Axiom, Pear, Lit Trade), social and pvp UIs (pvp dot trade, Senpi, FOMO), bots and signal apps (FlowBot, Tread fi, Moonbot, Hyperdash), based.app, defi.app and HIP-3 deployers. The registry is in miniapps hyperliquid frontends local builders dot json on the open mobula api repo. New addresses ship via public PR.
Why are some frontends at zero?
Three reasons. The frontend stopped operating or hasn't routed any attributed fills in the window. The frontend never enabled the builder code attribution system. The frontend uses a builder address not yet in our registry. The Time since last fill companion separates these cases. A frontend with hours of inactivity is in the first bucket. A frontend with consistent zero across all timeframes is in the second or third.
Why does Phantom Perps usually lead?
Consumer wallets integrate Hyperliquid trading directly inside the wallet UI. Their effective fee is typically in the 5 to 10 basis point range and the user base is large. The combination of wide reach times a moderate fee produces the highest absolute revenue. Pro terminals sit below because they charge less per dollar routed by design, even though their notional volume is comparable.
How often does the page refresh?
Every 30 seconds. The harness re reads the local hl node hourly file every 30 seconds and Prometheus scrapes the gauges on the same cadence. The page itself uses incremental static regeneration with a 60 second window, so headline values are at most 90 seconds stale plus chain propagation delay.
Can I cite a value from this page?
Yes. Every number is a Prometheus query exposed via the OCB API endpoints. The query string is visible in the row hover tooltip on the leaderboard. The harness source is open at the link in the source field below. Cite the value and the timestamp at the top of the page.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/hyperliquid-frontends