> For the complete documentation index, see [llms.txt](https://docs.reserve.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reserve.org/core-components/index-dtfs/fees/fee-distribution.md).

# Fee distribution

### Fee distribution <a href="#fee-distribution" id="fee-distribution"></a>

After platform fees are deducted, the remaining fees are distributed among the fee recipients according to their Admin-defined weights.

### Practical implications for users <a href="#practical-implications-for-users" id="practical-implications-for-users"></a>

#### For governance stakers <a href="#for-governance-stakers" id="for-governance-stakers"></a>

* Fee distribution to governance token holders follows an exponential distribution model over time to mitigate MEV (Miner Extractable Value) attacks
* Governance token holders can claim their pro-rata share of fees based on their staked tokens

#### For traders and holders <a href="#for-traders-and-holders" id="for-traders-and-holders"></a>

* When holding DTF tokens, be aware that the TVL fee continuously accrues, effectively acting as a management fee
* When minting new DTF tokens, account for the one-time mint fee in your calculations

#### For integrators <a href="#for-integrators" id="for-integrators"></a>

* Implement accurate fee calculations in your interfaces to provide users with precise token valuations
* Account for the continuous nature of the TVL fee when displaying token values
* Ensure your integration accounts for both fees when estimating transaction outcomes

### Governance implications <a href="#governance-implications" id="governance-implications"></a>

Fee parameters can be adjusted through governance, allowing the protocol to adapt to changing market conditions. This includes:

* TVL fee rate adjustments
* Mint fee rate adjustments
* Fee recipient configurations


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reserve.org/core-components/index-dtfs/fees/fee-distribution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.