{"slug":"hyperliquid-hip3-deployers","title":"Hyperliquid HIP-3 deployer revenue leaderboard","subtitle":"How much USD deployer fee revenue each HIP-3 builder-deployed dex collected over the rolling 24h, 7 day and 30 day windows. Data from a local hl node tailing every fill on mainnet.","category":"Trading","metric":"Deployer fees collected (USD)","unit":"usd","status":"live","higherIsBetter":true,"value":131374,"leader":{"name":"trade.xyz","slug":"xyz","value":131374},"rankings":[{"name":"trade.xyz","slug":"xyz","ms":{"p50":131374,"p90":6670630000,"p99":0.196944,"mean":113039},"successRate":100,"sampleSize":3621620},{"name":"HyENA","slug":"hyna","ms":{"p50":150.836,"p90":9920850,"p99":0.152039,"mean":232.871},"successRate":100,"sampleSize":12748},{"name":"Dreamcash","slug":"cash","ms":{"p50":94.2276,"p90":39204300,"p99":0.024035,"mean":523.145},"successRate":100,"sampleSize":3726},{"name":"Paragon","slug":"para","ms":{"p50":15.1915,"p90":96745.1,"p99":1.57026,"mean":32.5314},"successRate":100,"sampleSize":246}],"sparkline":[106035,101008,102011,102910,97988.8,99111.3,100767,99617.1,101327,102160,100967,101367,101744,100715,101169,101640,100381,101740,103458,100169,101887,103231,100836,102038,103825,103362,104308,105675,104164,104807,106373,102813,103311,103927,102316,102898,103701,101797,103044,104384,103482,104252,104896,103281,104770,106359,105580,106178,106747,105498,106293,107328,105274,106120,106963,102881,104827,107975,98563.9,107003,115853,107824,114111,119568,117179,121684,124515,123640,125772,127434,126196,128579,131374],"sampleSize":3638340,"asOf":"2026-07-01T17:58:55.646Z","headline":"trade.xyz leads deployer fees collected (usd) at $131.4K (24h) on Hyperliquid HIP-3 deployer revenue leaderboard.","quote":"trade.xyz leads deployer fees collected (usd) at $131.4K (24h) on Hyperliquid HIP-3 deployer revenue leaderboard. Source: OpenChainBench (https://openchainbench.com/benchmarks/hyperliquid-hip3-deployers).","cite":{"plain":"OpenChainBench. \"Hyperliquid HIP-3 deployer revenue leaderboard\". Retrieved 2026-07-01. https://openchainbench.com/benchmarks/hyperliquid-hip3-deployers","bibtex":"@misc{ocb_hyperliquid_hip3_deployers,\n  author = {OpenChainBench},\n  title  = {Hyperliquid HIP-3 deployer revenue leaderboard},\n  year   = {2026},\n  url    = {https://openchainbench.com/benchmarks/hyperliquid-hip3-deployers},\n  note   = {Retrieved 2026-07-01}\n}","apa":"OpenChainBench. (2026). Hyperliquid HIP-3 deployer revenue leaderboard. Retrieved July 1, 2026, from https://openchainbench.com/benchmarks/hyperliquid-hip3-deployers"},"pageUrl":"https://openchainbench.com/benchmarks/hyperliquid-hip3-deployers","ogImage":"https://openchainbench.com/api/og/hyperliquid-hip3-deployers","source":"https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/hyperliquid-frontends","methodology":["Data source. A local hl node operated on OCB infrastructure tails the Hyperliquid mainnet and writes every block of fills to node_fills_by_block hourly YYYYMMDD HH on local disk. Each line is one JSON block, the events array carries one entry per fill, and every fill on a HIP-3 market includes the dex namespaced coin (xyz:AAPL) plus the deployerFee in USDC.","Attribution. A fill belongs to a HIP-3 dex when its coin carries a namespace prefix (xyz:AAPL belongs to xyz). Namespaces are unique on chain by construction, so no hand curated registry is needed; the harness starts tracking a new deployer with its first observed fill, and the namespace is added to this page on the next spec review. Core Hyperliquid markets carry no namespace and no deployer fee, they are excluded.","Cadence. The Go harness re reads the current and previous hourly files every 30 seconds, parses appended lines, and updates per dex hourly buckets keyed by the UTC hour floor of the fill timestamp. Prometheus scrapes the metrics every 30 seconds via a Caddy reverse proxy with basic auth. End to end staleness from fill landing on chain to bench page render is typically under one minute.","Headline calculation. For each dex over the last 24 rolling hours we sum the deployerFee USD values of every fill on its namespaced markets. The 7 day and 30 day figures sum the same field over the last 168 and 720 hourly buckets, so the metric is consistent across the three ranges.","Volume companion. hl_hip3_deployer_volume_usd_24h, _7d and _30d are computed the same way on the px times sz product of every fill. They feed the Volume column and tab.","Users. Unique wallet addresses with at least one fill on the dex. The 24h figure is a union of per hour wallet sets over the rolling window; 7d and 30d are unions of per UTC day wallet sets. After a harness restart the day sets are reseeded from the on disk fill history before the 7d and 30d gauges publish, so they never lowball.","Markets. Count of distinct namespaced coins traded on the dex in the last 24 hours. A dex with 70 active equity markets and a dex with one commodity market are different products; the column makes that visible next to the revenue number.","Effective fee bps. Deployer fees divided by notional volume, times ten thousand, over the rolling 24h window. The trader perspective on what a representative dollar of flow paid the dex operator.","Window mechanics. Hourly buckets per dex go back 30 days in memory and are pruned on every publish. Per fill state is never retained; the largest dex clears about 4 million fills per day, so the bench aggregates at ingestion time instead of keeping fill level granularity.","30 day caveat. The node retains hourly fill files for a bounded horizon and the harness backfill reads what exists on disk. Until 30 full days of history accumulate, the 30d figures cover the available horizon and grow toward the full window.","Naming. Every namespace is resolved against the on chain perpDexs registry, which publishes the deployer address and full name: xyz is trade.xyz, vntl is Ventuals, cash is Dreamcash, km is Markets by Kinetiq, hyna is HyENA by the Based team, flx is Felix Exchange, para is Paragon. Attribution is by namespace prefix either way, so the numbers do not depend on naming.","Reproducibility. Harness source is open in the OCB harness tree. Anyone running their own hl node can clone, point the data flag at their node_fills_by_block hourly root, run the binary against a Prometheus scraper, and reproduce these metrics.","Failures. Any read error on the hourly files leaves the previous gauge values in place. Hourly bucket pruning is idempotent. Restarts replay the warmup window from disk before going live tail, and reseed the user sets from history in the background."],"license":"CC-BY-4.0"}