# Fees

Liminal operates with a **simple, transparent fee model**. Fees apply only to performance, execution, and cross-chain interactions.

**In summary:**

* **Customized:** 10% performance fees on gross funding & 1bp builder fees.
* **Tokenized xTokens:** 10% performance fees on profits and 0% management fees.
* **Tokenized limUSD:** 10% performance fees on profits at the limUSD level, in addition to the underlying xTokens’ performance fees.

**Customized product: Performance & Builder Fees**

* **Performance Fee:** 10% on gross funding profits, charged only when your strategy is profitable after execution costs (trading fees, spreads, etc.).
* **Builder Fee:** 1 basis point per transaction, covering operational overhead.

**Deposit & Withdrawal Fees**

Deposits and withdrawals for Liminal Customized (on Hyperliquid and Arbitrum) are free of protocol fees. Cross-chain deposits and withdrawals via deBridge, from Ethereum, Base, HyperEVM, or BNB Chain, incur a fixed 0.04% deBridge fee and a 0.02% Liminal fee.

**Trading & Execution Costs on Hyperliquid**

All execution (funding optimization, rebalancing, etc.) for Liminal Customized strategies is handled automatically by Liminal’s engine. All strategies run on Hyperliquid and follow its native fee structure:

* Based on 14-day trading volume and tier.
* Taker fees typically range from **0.045%** (base) to **0.024%** (high-volume).
* Maker rebates apply for large maker volumes.
* These fees are paid directly to **Hyperliquid**, not to Liminal.


---

# Agent Instructions: 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:

```
GET https://docs.liminal.money/more/fees.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.