# Canonical: https://www.uddalak.xyz/hyperliquid-academy/article/40-protocol-economics-fee-flow
# Author: Uddalak Das
# Last source: https://www.uddalak.xyz/hyperliquid-academy/article/40-protocol-economics-fee-flow

---
title: "Hyperliquid Protocol Economics and Fee Flow"
description: "Where trading fees come from, how different market types allocate them, and why protocol economics should be separated from token price narratives."
track: "Markets & Trading"
level: "Advanced"
primary_icp: ["institutional decision-maker", "DeFi-native user"]
secondary_icp: ["trader"]
reading_time: "3 min"
last_reviewed: "2026-09-07"
---

# Hyperliquid Protocol Economics and Fee Flow

Hyperliquid generates economic activity primarily when users trade, but not every fee follows the same path. Native markets, builder codes, HIP-3 markets, vaults, and other products can each introduce different recipients or revenue-sharing rules.

```mermaid
flowchart LR
    A[Trader executes] --> B[Trading fee]
    B --> C[Protocol-directed fee flow]
    B --> D[Builder fee if approved]
    B --> E[HIP-3 deployer share where applicable]
    F[Vault strategy] --> G[Vault PnL and applicable fees]
```

## Start with the fee schedule

Spot and perpetual trading fees depend on maker or taker status and rolling volume tiers. Incentives can change the effective cost for liquidity providers or high-volume users.

The exact schedule should always be treated as live protocol data rather than copied permanently into a research model.

## Builder codes create application revenue

A user can approve an additional builder fee for a frontend or application. If the user's trade includes the relevant builder code, that fee can be paid to the builder when execution occurs.

This lets trading interfaces monetize without becoming the exchange or taking custody of user funds.

## HIP-3 introduces deployer economics

Builder-deployed perp markets have their own economic relationship with the deployer. The current HIP-3 specification includes a deployer share of market fees alongside staking requirements and other responsibilities.

That changes the business model of market creation. A builder can operate market infrastructure and earn from activity, but must also manage oracle, market, liquidity, and operational risks.

## Revenue is not the same as token value

A rigorous protocol analysis should separate several questions:

1. How much economic activity does the protocol generate?
2. Which entities receive the associated fees?
3. What costs or liabilities sit against that revenue?
4. How, if at all, does the HYPE token capture value from those flows under current rules?

Skipping those steps turns protocol economics into token-price storytelling.

For institutional readers, the useful model is a flow-of-funds map that can be updated as fee tiers, HIP economics, and protocol policies change.

## Sources

- https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees
- https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes
- https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals