# Fees and economics

This page breaks down where every fee goes in a Berry Pool. It covers successful pools, wilted pools, and the ongoing Nectar fee.

### Berry protocol fees

* 1% of ETH collected, charged only on successful pools at harvest.
* 1% of deposited supply, charged only on successful pools at harvest.
* 2% of deposited supply, charged only on wilted pools at deadline.
* 10% of Nectar, which is the LP yield generated by Berry created LPs, charged for the life of the LP position.

### Where the rest goes

On a successful pool:

* 50% of the raised funds, after protocol fee, go to the dev.
* 50% of the raised funds, after protocol fee, become a permanent Uniswap V4 LP paired with the token.
* 99% of the deposited supply distributes to investors at harvest.

### On a wilted pool

* 100% of investor ETH is refunded, with no fees.
* 98% of the dev's deposited supply is returned.

### Worked example

1. A dev creates a pool with 18% of supply, a $200k target market cap, and a 10% bonus.
2. The effective entry market cap for investors is $180k.
3. The total ETH to raise, in USD equivalent, is roughly $32,400.
4. The pool fills to 100%, hits the target market cap, and completes cooldown.
5. Berry takes 1% of ETH, or $324, and 1% of supply.
6. The dev receives 50% of the remaining ETH, or roughly $16,038.
7. The LP is created with the other 50% of ETH paired with the deposited supply.
8. Investors receive their share of the project tokens proportionally.
9. Nectar begins flowing every 12 hours to all investors based on their token holdings.


---

# 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://docs.berryfi.org/berry-pools/fees-and-economics.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.
