> For the complete documentation index, see [llms.txt](https://docs.unstable.run/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unstable.run/launching-a-coin/overview.md).

# Launch overview

Everything happens in a **single transaction** to the Unstable Factory contract. That's not marketing — it's literally one `launchToken(…)` call. Here's what unfolds inside it, in order:

## The launch, step by step

1. **Pull USDT0.** The factory takes the $2 deploy fee (and, if you chose to buy in, your initial-buy budget) from your wallet.
2. **Deploy the token.** The factory does a `CREATE2` on `UnstableToken`, seeding the supply, decimals, and every metadata field you filled in.
3. **Create the V3 pool.** The factory calls the canonical Uniswap V3 Factory to spawn a fresh 1% fee-tier pool for `TOKEN / USDT0`, initialised at the fixed launch tick (\~$2K starting market cap).
4. **Mint the LP position.** The factory approves the NFPM and mints a **single-sided position** with 100% of the supply on the token side. The NFT lands directly in the LP locker contract — never in your wallet.
5. **Register in the locker.** The locker records the position's `tokenId`, your fee recipient (defaults to your wallet), and the treasury slot.
6. **Route the deploy fee.** The $2 USDT0 flows from the factory to the platform treasury.
7. **(Optional) Do the initial buy.** If you set `usdtIn`, the factory approves SwapRouter02 and does an atomic `exactInputSingle` from USDT0 into your new token, delivering the tokens to your wallet. Capped at **5% of supply** — even a huge budget can't buy more than that in the launch tx.
8. **Emit `TokenLaunched`.** All the metadata (name, symbol, logo, description, socials) plus positionId, starting tick, and timestamp land in a single event log. Indexers pick this up in one pass.

If any step fails, the whole transaction reverts — you either get a fully-live token or your USDT0 back.

## What you end up with

* An **ERC-20 token** at a `CREATE2`-deterministic address you can predict client-side.
* A **Uniswap V3 pool** at the 1% fee tier, initialised at the anchor tick.
* A **locked LP position** holding 100% of the supply, minted straight into the locker.
* An **on-chain metadata record** — name, symbol, logo (as an IPFS URI), description, and socials — all readable via getters on the token contract.
* Optionally, a **bag of your own token** in your wallet, if you chose to include an initial buy.

## What it costs

|                                          | Amount                                |
| ---------------------------------------- | ------------------------------------- |
| Deploy fee (to platform treasury)        | **$2 USDT0**                          |
| Optional initial buy (to you, as tokens) | Whatever you choose, up to the 5% cap |
| Gas (paid in USDT0)                      | \~$0.02-$0.05                         |

## What you keep forever

* **80% of every trade's 1% pool fee**, collectable at any time by anyone (funds route to the fee recipient you set at launch).
* **The metadata slot** — nobody can rename your token, change its logo, or swap the socials. Everything's immutable.
* **The right to trade**, obviously.

## What next

* [Creating your coin](/launching-a-coin/creating-your-coin.md) — every form field explained
* [Optional initial buy](/launching-a-coin/initial-dev-buy.md) — the 5% cap, why it exists, how to size it
* [After the launch](/launching-a-coin/after-launch.md) — what happens in the minutes and hours after the tx confirms


---

# 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.unstable.run/launching-a-coin/overview.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.