> For the complete documentation index, see [llms.txt](https://docs.retro.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.retro.finance/tokenomics/fee-structure.md).

# Fee Structure

As Retro features concentrated liquidity pools exclusively, the fee tier will vary from pair to pair.

If both tokens of a liquidity pool's pair are whitelisted by Stabl Labs to be staked in gauges and receive $oRETRO emissions rewards, the liquidity providers of that pair will not receive swap fees. The profits expected by the liquidity providers staking on gauges are solely derived from $oRETRO emissions. 

In contrast, veRETRO holders who vote to incentivize a particular gauge with emissions will receive swap fees from the liquidity pair that they voted for. This creates the incentives for veRETRO lockers to vote for the gauges that produce the highest volume in swap fees. The amount of fees earned by veRETRO holders depends on the pool that they vote for. Trading fee distribution is as follows:

{% hint style="info" %}
Pools - 

* 78.33% fees to veRETRO voters
* 13% ALM fee 
* 8.67% sent to Overcollateralization (OC) Treasury to increase the yielding power of $CASH<br>
  {% endhint %}

Through this mechanism, the system provides veRETRO holders with the power to incentivize swap fees instead of total liquidity. The destination of $oRETRO emissions is in the hands of the lockers.

If a liquidity pool is not whitelisted to be staked in the gauge, it will receive all the swap fees it generates but have no $oRETRO emissions.&#x20;

<br>


---

# 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.retro.finance/tokenomics/fee-structure.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.