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

# Launch a Token

One transaction. No presale, no team allocation, no code.

## What you set

| Field                          | Notes                                                                                                                                                                                         |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name & ticker**              | On-chain, permanent.                                                                                                                                                                          |
| **Logo, description, socials** | Uploaded to IPFS and referenced on-chain via `metadataURI`. Optional but recommended — it's how your token looks on the board.                                                                |
| **Paired with**                | What your token trades against: **ETH**, **USDG** (dollars), or a tokenized stock — **NVDA, AAPL, GOOGL, TSLA, AMZN**. See [Stock Pairs](/product/stock-pairs.md).                            |
| **Buyback & burn**             | Toggle the loop on and pick its size: 5–90% of every trade's fee. **Locked forever at launch** — see [Buyback & Burn](/product/buyback-and-burn.md).                                          |
| **Your first buy**             | Optional ETH amount to buy in the same transaction as the launch — before any sniper can. Hard-capped at **5% of supply**, enforced on-chain. The **MAX** button fills the exact cap for you. |

## What happens on-chain

1. Your token is deployed: **1,000,000,000 supply**, minted once, no further minting, no pause, no blacklist. Plain ERC-20 + burn.
2. A Uniswap v4 pool is created and initialized at a price anchoring the starting market cap at **\~$4,000**.
3. **100% of the supply** goes into a single-sided liquidity position — there is no team vault or reserve. The LP NFT is locked in the LP manager.
4. If buyback is on, its share of the fee is registered in the pool's hook — immutably.
5. Your first buy (if any) executes atomically in the same transaction. Whatever the route, the contract reverts if you'd receive more than 5% of supply.

## After launch

* Your token appears on the board instantly and is indexed by DexScreener as a standard Uniswap v4 pair.
* You earn **60% of LP fees** on every trade, claimable any time — see [Fees & Creator Earnings](/product/fees-and-earnings.md).
* Nothing about the token can be changed by anyone: supply, fees, buyback share and liquidity are all fixed at launch.

## Costs

Launching costs a single transaction fee (typically under a cent) plus whatever you choose to spend on your first buy.


---

# 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.loopad.fun/product/launch-a-token.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.