> For the complete documentation index, see [llms.txt](https://docs.pangolin.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pangolin.exchange/pangolin-overview/introduction-to-pangolin/pangolin-v3/multiple-fee-tiers.md).

# Multiple Fee Tiers

{% hint style="info" %}
**Note for Developers**: Because Pangolin V3 allows fee adjustments, a pool’s fee tier isn’t permanently fixed after creation – it can be updated to a different rate if needed, unlike Uniswap V3’s immutable fee tier per pool.
{% endhint %}

When adding a new liquidity position in Pangolin V3, users can choose from several **predefined fee tiers** for that pool. Each tier is suitable for different types of pairs – lower fees for very stable pairs, higher fees for volatile pairs – to balance trader cost and LP reward.\
\
Pangolin’s innovation is that it does not impose rigid restrictions on these tiers: the team can **strategically manage and adjust fees for key pools** without needing a protocol upgrade. In practice, governance or the Pangolin team may add new fee tiers or tweak fees on important pairs to remain competitive and attract liquidity.\
\
This flexibility means essential pools can maintain attractive fee structures that quickly respond to market changes.&#x20;


---

# 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.pangolin.exchange/pangolin-overview/introduction-to-pangolin/pangolin-v3/multiple-fee-tiers.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.
