> For the complete documentation index, see [llms.txt](https://stonkfun.gitbook.io/stonkfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkfun.gitbook.io/stonkfun-docs/core-concepts/fee-models.md).

# Fee models

A launch's fee model decides who earns from it, and it is fixed permanently at creation.

![The fee model selector](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-0681d4f3b1e30569431df40a1d311cb9b7f2c963%2Flaunch-fee-model.png?alt=media)

## The two families

|                        | Fee coin (`standard`)                       | Reward coin (`reward`)                |
| ---------------------- | ------------------------------------------- | ------------------------------------- |
| Creator earns          | Yes, from a locked position they claim from | No creator position at all            |
| Holders earn           | No                                          | Yes, automatically, on every transfer |
| Pool trading fee       | 1% or 2%                                    | 1%                                    |
| Extra friction         | None                                        | A 1% or 3% transfer tax               |
| Second Fee Key goes to | The creator's wallet                        | The Ecosystem Flywheel                |

## Standard, 1% tier

The default. Two identical locked positions with equal liquidity and identical ticks, and the creator's Fee Key is minted straight to the wallet that paid for the launch.

Raydium splits a 1% pool's fee three ways: 84% to LP positions, 12% to its own buybacks, and 4% to its treasury. Since the two launch positions hold equal liquidity, each takes half of the LP share:

* Creator: about 0.42% of swap volume
* Platform: about 0.42% of swap volume

## Standard, 2% tier

The same shape, but the pool runs on the 2% tier and liquidity splits 25% platform, 75% creator.

That split is chosen deliberately. A 25% share of a 2% pool is 0.5% of every trade, which is exactly the same platform revenue as half of a 1% pool, while the creator's 75% is worth 1.5%. The higher creator cut comes out of the trader's fee, not out of the platform's share.

Over the API this is the optional `feeTier: '2%'` field on `/launches/prepare`. It is rejected on reward launches.

## Reward coin

A reward launch is a Token-2022 mint carrying an immutable transfer tax, trading on a 1% pool.

| Property         | Value                                    |
| ---------------- | ---------------------------------------- |
| Transfer tax     | 1% by default, or 3% by choice at launch |
| Pool tier        | 1%                                       |
| Liquidity split  | 90% platform, 10% Ecosystem Flywheel     |
| Creator position | None                                     |

Total trading friction at the default rate is 2%, being the 1% pool plus the 1% tax.

The tax is paid on every transfer, on any venue, including wallet-to-wallet transfers. The rate is locked at creation and can never be changed afterwards.

The flywheel's 10% share earns 0.1% of pool volume, which is pooled across every reward launch and spent buying back and burning the platform's top tokens. See [The Ecosystem Flywheel](/stonkfun-docs/earning/ecosystem-flywheel.md).

## Where fees accrue

On newer pools, all trading fees accrue in the quote token rather than being split across both sides of the pair. Which behaviour a pool has is fixed when the pool is created and cannot be changed afterwards, so it is recorded per launch and every claim, reward and burn path reads it from there. Older pools keep collecting on both sides exactly as they always have.

For a creator this only affects what arrives when you claim: either both tokens of the pair, or the quote token alone.

## The split is verified, not assumed

Both positions span identical ticks, so each Fee Key's share of trading fees is proportional to the liquidity it holds. Before either position is locked, the realised split is read back from the chain and checked against the target. Standard launches are checked for exact equality; the others are checked within a tolerance tight enough to catch a real mistake.

A launch cannot be re-run, so this is the last chance to catch a mismatch before it becomes permanent.


---

# 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://stonkfun.gitbook.io/stonkfun-docs/core-concepts/fee-models.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.