> For the complete documentation index, see [llms.txt](https://docs.trade.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trade.xyz/events/fees.md).

# Fees

Hyperliquid outcome-trading fees for Events.

The `txyz` initial launch configuration sets `deployerFeeScale = 0` for every standalone outcome or question. Outcomes added to a question inherit the question’s scale. At scale zero, the market adds no deployer fee and `txyz` receives no deployer fee share. Events users pay Hyperliquid’s base outcome-trading rates, which use the spot fee schedule.

Outcome trading charges fees when a position is closed or settled, not when it is opened. Only fee-paying outcome volume counts toward a user’s volume tier. Outcome trading does not support maker rebates. A maker order that would otherwise qualify for a rebate pays zero instead.

One fee tier applies across a user’s perps, HIP-3 perps, and spot activity. Hyperliquid assesses the tier daily in UTC. Fee-paying outcome volume counts toward the tier; Hyperliquid’s current fee documentation controls its weighting. The user’s applicable HYPE staking discount is reflected in the rate shown for that user.

## Base outcome rates

|          |                         | Base Rate |        | Diamond |         | Platinum |         |    Gold |         |  Silver |         |  Bronze |         |    Wood |         |
| -------- | ----------------------: | --------: | -----: | ------: | ------: | -------: | ------: | ------: | ------: | ------: | ------: | ------: | ------: | ------: | ------: |
| **Tier** | **14d weighted volume** |     Taker |  Maker |   Taker |   Maker |    Taker |   Maker |   Taker |   Maker |   Taker |   Maker |   Taker |   Maker |   Taker |   Maker |
| 0        |                       — |    0.070% | 0.040% | 0.0420% | 0.0240% |  0.0490% | 0.0280% | 0.0560% | 0.0320% | 0.0595% | 0.0340% | 0.0630% | 0.0360% | 0.0665% | 0.0380% |
| 1        |                    >$5M |    0.060% | 0.030% | 0.0360% | 0.0180% |  0.0420% | 0.0210% | 0.0480% | 0.0240% | 0.0510% | 0.0255% | 0.0540% | 0.0270% | 0.0570% | 0.0285% |
| 2        |                   >$25M |    0.050% | 0.020% | 0.0300% | 0.0120% |  0.0350% | 0.0140% | 0.0400% | 0.0160% | 0.0425% | 0.0170% | 0.0450% | 0.0180% | 0.0475% | 0.0190% |
| 3        |                  >$100M |    0.040% | 0.010% | 0.0240% | 0.0060% |  0.0280% | 0.0070% | 0.0320% | 0.0080% | 0.0340% | 0.0085% | 0.0360% | 0.0090% | 0.0380% | 0.0095% |
| 4        |                  >$500M |    0.035% | 0.000% | 0.0210% | 0.0000% |  0.0245% | 0.0000% | 0.0280% | 0.0000% | 0.0298% | 0.0000% | 0.0315% | 0.0000% | 0.0333% | 0.0000% |
| 5        |                    >$2B |    0.030% | 0.000% | 0.0180% | 0.0000% |  0.0210% | 0.0000% | 0.0240% | 0.0000% | 0.0255% | 0.0000% | 0.0270% | 0.0000% | 0.0285% | 0.0000% |
| 6        |                    >$7B |    0.025% | 0.000% | 0.0150% | 0.0000% |  0.0175% | 0.0000% | 0.0200% | 0.0000% | 0.0213% | 0.0000% | 0.0225% | 0.0000% | 0.0238% | 0.0000% |

## HYPE staking tiers

| Tier     | HYPE staked | Trading-fee discount |
| -------- | ----------: | -------------------: |
| Wood     |         >10 |                   5% |
| Bronze   |        >100 |                  10% |
| Silver   |      >1,000 |                  15% |
| Gold     |     >10,000 |                  20% |
| Platinum |    >100,000 |                  30% |
| Diamond  |    >500,000 |                  40% |

For the treatment of minting, ordinary trades, burning, and settlement, see Hyperliquid’s current [fee documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees#outcome-tokens).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trade.xyz/events/fees.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.