Hyperliquid Builder Codes for Charging Fees on User Trades
Summary
This document explains how Hyperliquid builder codes let an application builder charge a fee on fills from orders submitted on a user's behalf. Users first authorize a maximum fee for a builder; the authorization must come from the user's main wallet and can later be revoked. An order may then specify the builder and fee amount. The document describes perps and spot fee limits, notes that spot applicability is restricted to fees collected in quote or collateral assets, and says builder fees on perpetual trades apply to both sides.
Builders must meet an account-value requirement and use standard account abstraction. The document also outlines how builders claim collected fees and how users can query approvals and fee totals, with fill records available through daily data files. These details describe protocol mechanics rather than a trading strategy or performance result. Implementers should account for the stated limits, the cap on active approvals, and case-sensitive builder identifiers when retrieving fill data.
Key ideas
- Users authorize a maximum builder fee for each builder and can revoke that approval.\nThe approval must be signed by the user's main wallet.\nBuilder fee caps differ between perpetual and spot trades, and spot coverage is limited by the asset in which fees are collected.\nA builder needs the specified account value and account abstraction mode to use builder codes.\nApproval status, collected fees, and builder fills can be queried through the documented information and data interfaces.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.