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

# Fee Structure

FIVA charges two simple fees to support protocol development and reward liquidity providers.

### Fee Breakdown

#### 1. Yield Fee: 5%

**What**: 5% of all yield generated goes to the protocol\
**Who pays**: Only YT (Yield Token) holders\
**Example**: If underlying yield is 10%, YT holders receive 9.5%\
**Note**: PT holders pay no yield fees

#### 2. Trading Fee: 0.1%

**What**: 0.1% fee on all trades through FIVA pools\
**Split**:

* 0.07% to liquidity providers
* 0.03% to protocol

**Example**: Trade 1,000 TON → pay 2 TON fee

### Who Pays What

| User Type               | Yield Fee   | Trading Fee            |
| ----------------------- | ----------- | ---------------------- |
| **YT Holders**          | 5% of yield | 0.1% when trading      |
| **PT Holders**          | None        | 0.1% when trading      |
| **Liquidity Providers** | N/A         | Earn 0.06% from trades |
| **Traders**             | None        | 0.1% per trade         |

### **Conclusion**

 FIVA's fees are designed to be fair, transparent, and competitive while ensuring the protocol can continue improving and expanding.


---

# 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.thefiva.com/fiva-mechanics/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.