> 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/launching/launch-costs.md).

# Launch costs

The launch fee is a measured cost model rather than a margin. It is what creating the launch actually costs on-chain, plus a small buffer.

Current figure: **about 0.29 SOL**.

![The launch summary panel shows the exact cost before you sign](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-fb5111f0f58c00095f4f0b4a58820b9e3ebee50e%2Flaunch-summary.png?alt=media)

## What you are paying for

Almost all of it is Solana rent, paid once, for accounts that exist forever:

* The Raydium pool and its price oracle
* The tick arrays that define the position's price range
* The two pool vaults
* Two position accounts, and the lock record and Fee Key NFT for each
* The token mint and its metadata
* Permanent Arweave storage for your logo and metadata
* Transaction fees for the launch itself

The oracle account and the two tick arrays alone are over 60% of the total.

## Why it is not cheaper

The launch already skips cosmetic metadata for the temporary position NFT. What it will not skip is immutable token metadata, permanent Arweave storage, the wide liquidity range, and Burn & Earn locking on both positions.

Materially lower costs would mean giving up one of those guarantees.

## It does not scale with anything

The fee is the same regardless of which quote token you pick or how wide the price range is. Raydium positions are continuous, so the same handful of accounts covers any range.

## Add-ons

| Add-on                                                   | What it adds                                                    |
| -------------------------------------------------------- | --------------------------------------------------------------- |
| [Dev buy](/stonkfun-docs/launching/dev-buy.md)           | The curve price of your buy plus the pool's trading fee, in SOL |
| [Airdrop mode](/stonkfun-docs/launching/airdrop-mode.md) | Roughly 0.00213 SOL per recipient, mostly account rent          |

Both are quoted in full before you sign and are included in the single payment you make.

## What you get back

Nothing, and that is by design. Pool, oracle and tick-array accounts are permanent, and position rent is locked with the position forever.

The distinction that matters is that a dev buy comes back to you as tokens, and an airdrop's cost buys the accounts your recipients need. The rest is the price of a market that cannot be pulled.


---

# 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/launching/launch-costs.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.
