A builder code lets an application that routes orders to Hyperliquid attach a small fee to those orders, paid by the user to the application. It’s how third-party interfaces, bots and platforms earn revenue on the venue without holding user funds.
How it works
The user approves a maximum builder fee once, for a given application. From then on, orders placed through that application can carry a fee up to that cap. The fee is collected by Hyperliquid and paid to the builder’s address.
The user never pays more than they approved, and can revoke the approval at any time.
Why it exists
Hyperliquid is a protocol, not a product. Interfaces, automation and strategy platforms are built by others, and builder codes give them a revenue model that doesn’t require custody. The alternative would be applications taking deposits — which is the custody risk the whole architecture avoids.
Builder codes versus referrals
A referral code gives the referrer a share of the protocol’s own fee. A builder code adds a separate fee on top, set by the application, paid to it. Referrals reward introductions; builder codes pay for software.
What it means for AlphaNet
Strategy deployment on Hyperliquid runs through this mechanism. Users approve a capped fee, orders carry it, and revenue arrives without any capital changing hands. It’s why AlphaNet can operate on a wallet it doesn’t control.