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

# Fees

**Runes** **DEX Fee is 2%** 

• 80% of this goes to liquidity providers

• 20% of this goes to treasury. 

**We want to minimize the amount of UTXO in user swap transactions, therefore following scheme is proposed:** 

• DEX Fees = LP Fees + Treasury Fees. 

• DEX fees are collected in both bid & ask assets. Total fee is 2%, so we take 1% of bid asset and 1% of ask asset. 

• DEX backend will keep track of treasury earnings in its database. Physically, coins will be located on a pool wallet (and controlled by pool wallet) and can be withdrawn by treasury wallet owner later in a separate withdraw operation. These coins will not be reinvested (e.g. added to pool balance in a database). Technically, when treasury withdraws, then network fee can be deducted from its BTC earnings. 

• LP Fees will be reinvested, and LP providers can withdraw them by doing remove liquidity.


---

# 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://docs.runesdex.com/products/exchange/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.