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.

Get your wallet briefing
Scan wallet No extension? Paste instead

MetaMask or Rabby returns the selected public account. No private key, agent wallet, transaction, or message signature.

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. Connect walletMetaMask or Rabby returns the selected public account. Paste remains a fallback.
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.

Evidence standard

Hyperdaily separates public protocol facts from product interpretation, labels stale or missing evidence, and keeps connection separate from signing. Read the full data and scoring methodology.

Related Hyperdaily pages

Hyperliquid wallet scannerHyperliquid agent walletsHyperliquid copy trading, read-only firstHyperdaily glossary

Want this read against your own wallet?

Paste an address, get the briefing