Hyperliquid builder codes tag every order an app sends, and the exchange pays that app a builder fee on each fill. This table sums HyperCore fills per UTC day, builder code, market and fee token: fills, distinct traders, volume, and the fee split between the builder, the HIP-3 deployer and the exchange. Fills sent without a builder code are in the same table with an empty Builder_Address, so shares add up to the whole exchange.
Most buyers sum Volume and Builder_Fees by Builder_Address over a week, or filter Market_Kind = 'hip3' to rank stock perps by volume and deployer fees. On 11 November 2026 builder-coded fills were $1.40 billion of $20.36 billion in fill volume and paid $423,000 in builder fees. Builder codes are addresses; we do not attach app names.
Use cases
Rank apps by Hyperliquid volume routed through their builder codes
Builder fee revenue per app, market and day
HIP-3 deployer fees and volume per stock, index and commodity perp
Share of exchange volume that comes through front ends and bots
Table
15 columns · free sample for the table
hyperliquid_builder_fees_daily
15 columns
One row per UTC day, builder code, market and fee token: fills, traders, volume and the fee split between builder, HIP-3 deployer and exchange.
hyperliquid/hyperliquid-builder-fees/hyperliquid_builder_fees_daily<YYYY-MM-DD>.parquetone file per UTC day
Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief ↗ first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Delivery
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# hyperliquid_builder_fees_daily: one file per UTC day
hyperliquid/hyperliquid-builder-fees/hyperliquid_builder_fees_daily<YYYY-MM-DD>.parquet
Download a free sampleNo email needed.
Pay nowName, work email and licence check.
Pay the invoiceBy card or bank transfer.
Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.
Need new data after your purchase?
Kafka Streams sends new Hyperliquid data in real time, so your copy can stay current after the files end. It is sold on an Enterprise plan.
One table, hyperliquid_builder_fees_daily, with 15 columns. Each row is one UTC day, builder code, market and fee token, with fills, taker fills, traders, volume and four fee columns. Plain perps, spot and HIP-3 perps from the xyz, io, para and mkts dexes are covered. Liquidation fills are left out.
How big is it?
About 12,000 to 13,000 rows a day, so around 380,000 rows for 30 days. One day is about 600 KB of ZSTD Parquet, so the whole window is around 18 MB. These are estimates from our 14 November 2026 sample; the delivery manifest gives exact figures.
Which apps route the most Hyperliquid volume?
Filter Builder_Address <> '' and sum Volume and Builder_Fees grouped by Builder_Address. On 11 November 2026, 536 builder codes had fills. The table gives addresses only, so match them to apps from the builders' own announcements.
Which stocks trade on Hyperliquid?
Filter Market_Kind = 'hip3' and group by Market_Protocol and Market_Symbol; the xyz dex lists most stock perps, as xyz:NVDA, xyz:TSLA and so on. Sum Volume for activity and Deployer_Fees for what the deployer earned.
How are the fees split?
Total_Fees is the fee on the fill and already includes the builder fee and, on HIP-3 markets, the deployer fee. On an ETH taker fill we checked, the fee was 8.67 basis points of notional, of which 5 went to the builder. On an xyz:NVDA taker fill it was 5.86 basis points: 5 to the builder, 0.39 to the deployer, the rest to the exchange.
How are the numbers checked?
The Fills total for a day equals the number of fill rows in our HyperCore trades table for that day: 13,148,003 on 11 November and 13,255,502 on 12 November 2026.
What limits should I know about?
Volume counts each side of a match, so the sum over all rows is twice the matched volume. Fees on spot are in the received token, so sum fees within one Fee_Token. HIP-3 dexes margined in USDH, USDE or USDT0 (km, flx, vntl, hyna, cash) are not in our HyperCore feed yet.
How do I load it?
With DuckDB: SELECT Builder_Address, sum(Volume), sum(Builder_Fees) FROM read_parquet('hyperliquid_builder_fees_daily/*.parquet') WHERE Builder_Address <> '' GROUP BY 1 ORDER BY 2 DESC. With pandas: pd.read_parquet('hyperliquid_builder_fees_daily/').
How far back does it go and how is it delivered?
30 days, the rolling window our HyperCore history keeps, up to the day before we prepare the files. Files are Parquet, one per UTC day, ZSTD-compressed, in a Requester Pays S3 bucket; download costs are billed to your AWS account.