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

# Fees

{% hint style="info" %}
HyperStackz uses a performance-based fee model built around **Limit-Order Execution** and **Builder Codes**.\
Strategies are designed to minimize costs, avoid taker fees, and reward both users and builders only when real profit is generated.
{% endhint %}

***

### Limit-Order Based Execution

Every order in HyperStackz is executed using **limit orders**, except entries. \
This ensures trades occur efficiently on the **Hyperliquid order book** while avoiding unnecessary fees.

**Core Execution Behavior**

* All entries are placed as Market Taker
* This refresh logic ensures fills remain efficient without crossing the spread.
* Each AVG down & TTP are placed as Limit Orders

***

### Fee Optimization

Using limit orders means you’re **adding liquidity**, not taking it.\
This provides two major benefits over typical bots that execute with market orders:

* **Reduced Fees:** Maker fees are substantially lower than taker fees.
* **Rebate Potential:** Once a user generates enough maker volume within a 14-day period, effective fees can drop to **0%** or even become **positive rebates**.

{% hint style="success" %}
Consistent activity can push your account to the highest Hyperliquid tier —\
earning rebates instead of paying trading fees.
{% endhint %}

***

### Builder Codes & Performance Fees

Each strategy you launch is tied to a **Builder Code**, which defines its configuration and fee logic.\
Builder fees are only charged when a strategy completes a profitable cycle — never on deposits, never on losses.

**How Builder Fees Work**

* When a **TTP (Trailing Take-Profit)** triggers and the strategy closes in profit,\
  a small percentage of that realized yield is paid as a **Builder Fee**.
* The fee is distributed automatically and tracked through the Builder Code linked to your strategy.
* If the cycle does not reach TTP or closes at breakeven or loss, **no fee is charged**.

{% hint style="info" %}
Builder Codes connect the ecosystem — rewarding developers and strategists for profitable execution\
without burdening users with upfront or idle fees.
{% endhint %}

***

### Why Builder Fees Matter

Builder Codes enable decentralized growth and transparent revenue sharing between the HyperStackz platform, strategy creators, and users.\
This structure ensures that all incentives align with profitable outcomes — not simply trade volume.

| Trigger Event                 | Fee Type             | Description                                          |
| ----------------------------- | -------------------- | ---------------------------------------------------- |
| **TTP Triggered with Profit** | Builder Fee          | Applied only on realized yield; shared with builder. |
| **Unprofitable Cycle**        | No Fee               | No deduction or platform cost.                       |
| **Limit Order Execution**     | Maker Fees / Rebates | Managed automatically by engine (Hyperliquid side).  |

***

### Summary

HyperStackz is built around performance, efficiency, and fairness:

* **Limit-Order Execution:** Trades placed at mid-price and refreshed every 5 seconds.
* **Fee Reduction:** Maker-side execution minimizes or removes fees entirely.
* **Rebates:** High-volume activity earns liquidity rebates every 14 days.
* **Builder Codes:** Performance-based fees only on profitable cycles, never on deposits or losses.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hyperstackz.gitbook.io/hyperstackz-docs/strategy-mechanics/fees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.