> For the complete documentation index, see [llms.txt](https://polydash.gitbook.io/polydash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-fees.md).

# Fund fees

Every fee on a fund is written into the contracts or into the template that the fund copied. This page lists them.

| Fee             | Rate                                                          | Who sets it              | Notes                                                                                                                                 |
| --------------- | ------------------------------------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| Protocol fee    | 0.2% (20 bps) of mint ETH                                     | Fixed in code, no setter | Paid to the factory's fee recipient when anyone calls `withdrawProtocolFee`. The factory owner can change the recipient, not the rate |
| Entry fee       | 0% to 5% (0 to 500 bps) of mint ETH                           | Manager, at creation     | Optional. The manager pulls it to a payout wallet. It never sends principal                                                           |
| Performance fee | Set by the template. Published templates range from 0% to 20% | Template                 | Charged only on gains in net value per share above the high-water mark. `harvest` accrues it, and the manager pulls it                |
| Exit fee        | None                                                          |                          | The Phase 3 vault has no separate exit-fee field                                                                                      |
| Swap costs      | Router and pool fees                                          | Third-party routers      | Paid out of the fund when it trades                                                                                                   |

## How the fees are taken

* On mint, the protocol fee and the entry fee are each rounded down out of the gross amount. What remains is `principal`.
* A performance fee accrues only on net value per share above the previous high. A fund that falls and recovers does not pay twice on the same gain.
* Fees are pulled by their recipients. They are not pushed during a mint or an exit.

## What fees are not

Fees are costs of a mechanism. They are not a forecast of any outcome.

## Related

* [Strategy templates](https://polydash.gitbook.io/polydash-docs/polypad-funds/strategy-templates.md)
* [Create a fund](https://polydash.gitbook.io/polydash-docs/polypad-funds/create-a-fund.md)


---

# 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://polydash.gitbook.io/polydash-docs/polypad-funds/fund-fees.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.
