> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/protocol/creator-fees.md).

# Creator Fees

Hatchr pools use the Uniswap V3 **1% fee tier**. This is a pool-level swap fee, not a tax implemented by the token.

## Current split

When the position is registered, the locker stores:

* creator fee wallet;
* Hatchr platform fee wallet; and
* creator fee percentage.

The current split is:

| Recipient | Share of collected LP fees |
| --------- | -------------------------: |
| Creator   |                        40% |
| Hatchr    |                        60% |

## Fee flow

```mermaid
flowchart LR
    A[Uniswap V3 swaps] --> B[1% pool fees]
    B --> C[Locked position]
    C -->|claimFees| D[LPLocker]
    D -->|40% current split| E[Creator fee wallet]
    D -->|60% current split| F[Platform fee wallet]
```

The creator does not receive 1% of each trade directly. Fees first accrue to the LP position and are divided when collected.

## Assets received

Claims may contain the launched token, WETH or both. The exact assets depend on token ordering and trading activity.

## Permissionless claim call

Anyone can trigger `claimFees(positionTokenId)`. The caller cannot choose the recipients. The locker sends proceeds only to the recipients stored for that position.

{% hint style="info" %}
The creator percentage is owner-configurable for future position registrations. Read the factory and registered locker position rather than assuming the split.
{% endhint %}


---

# 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.hatchr.fun/protocol/creator-fees.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.