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

# Dex Fees

### v3 Pools

When a new V3 pool is created, the pool creator selects a fee tier. This fee tier becomes the total swap fee paid by traders for every swap in that pool.

Fee distribution:

* Liquidity Providers (LPs): 86% of the selected fee tier
* Protocol / Treasury: **14% of the selected fee tier**

Example – 0.30% fee tier:

* LPs receive 0.258% of the traded amount
* Protocol receives 0.042% of the traded amount
* The trader pays 0.30% total

Key points:

* The pool creator, not a central authority, chooses the fee tier.
* A 14% protocol fee share is always active on Hypertrade-integrated V3 pools.
* LPs always receive the majority (86%) of whatever fee tier is chosen.

### v2 Pools

All V2 pools operate with a fixed base fee of 0.30% per swap.

Fee distribution:

* LPs receive 5/6 of the fee
* Protocol (feeTo) receives 1/6 of the fee

In percentage terms:

* Total fee paid by the trader: 0.30%
* Protocol share: 0.30% × (1/6) = 0.05%
* LP share: 0.30% × (5/6) = 0.25%


---

# 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.ht.xyz/hypertrade-dex/dex-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.
