Fee routing without mystery
Hyperliquid builder codes
Builder codes let Hyperliquid applications attribute routed fills and earn a small user-approved fee. Hyperdaily keeps that second: scan first, preview the fee, then sign approveBuilderFee only if the route is worth it.
What this page solves
- Understand what a builder code can charge before signing anything.
- See why approveBuilderFee belongs behind a wallet-specific preview.
- Keep revoke/lower-to-zero visible instead of hiding builder permissions.
How Hyperdaily handles it
1. Paste walletUse a public 0x address or browser wallet account request.
2. Read live contextFunding, whales, vaults, HyperEVM, risk, and local decision memory.
3. Preview before signingAny vault, builder, or agent action gets a separate preview and revoke path.
FAQ
What is approveBuilderFee?
It is a user-signed Hyperliquid permission that sets the maximum builder fee an application can attach to routed orders.
Does scanning approve a builder code?
No. A Hyperdaily scan is read-only. Builder approval is a separate preview and signature step.
Can the fee be revoked?
Yes. The safe path is an approveBuilderFee update to zero or a lower cap, with the change recorded for the user.
Related Hyperdaily pages
Ready to check a wallet?
Open the live Hyperdaily scanner