> 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/tvl-fee.md).

# TVL fee

### TVL fee explained <a href="#tvl-fee-explained" id="tvl-fee-explained"></a>

The TVL fee is expressed as a percentage of the DTF's Total Value Locked and is applied continuously through a compound interest calculation.

#### Technical implementation <a href="#technical-implementation" id="technical-implementation"></a>

The TVL fee is implemented using a compound interest formula:

```
fee = (1 / (1 - feePerSecond))^secondsPassed - 1
```

Where:

* `feePerSecond` is set by the DTF Owner (governance)
* `secondsPassed` represents the time since the last fee calculation

This mechanism ensures that:

* The fee is calculated and accounted for on every user interaction
* Any view functions account for the TVL fee since the last contract update
* The fee accumulates continuously rather than at discrete intervals

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

For users and integrators, this means:

* The TVL fee effectively acts as a continuous management fee
* The longer assets remain in the DTF, the more fees accrue
* The displayed value of Index DTF tokens will gradually decrease relative to the underlying assets, reflecting the accrued fees


---

# 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/tvl-fee.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.