# Fees

Swap fees play a crucial role in Magma Protocol. In Magma, there are many fee tiers, from 0.001% to 1%.

Magma Protocol implements a fee structure where a percentage of the trade amount is charged as a fee. For example, a common fee might be set at **0.25%** of the transaction value. This fee is automatically deducted from the trade.

Here are the key reasons for this structure:

1. **Risk Compensation**: Different trading pairs exhibit varying levels of volatility. Lower fee tiers (e.g., 0.01% or 0.05%) are suitable for stablecoin pairs with minimal price fluctuations, while higher fees (e.g., 1%) are appropriate for more volatile pairs. This allows LPs to choose fee structures that align with their risk appetite.
2. **Liquidity Optimization**: LPs can select fee tiers based on expected trading volume and volatility, optimizing their capital allocation. Higher fees attract cautious LPs seeking greater returns, while lower fees can drive more trading volume, benefiting those with lower risk exposure.
3. **Market Dynamics**: Multiple fee tiers create a competitive environment where traders can choose pools that best suit their needs. This flexibility encourages diverse trading activities and enhances overall market efficiency.
4. **Fragmentation Management**: Although multiple fee tiers could lead to liquidity fragmentation, concentrated liquidity model allows LPs to target active trading ranges effectively, minimizing the impact on price execution.

### Fee Distribution

Fees will be distributed to liquidity providers pro-rata.

A 20% protocol fee will be charged by the protocol.


---

# 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://magma-finance-1.gitbook.io/magma-finance/product/clmm/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.