# Launching a token

## What you need

* A connected TON wallet.
* \~0.6 TON in the wallet (0.5 TON for the launch tx + a little for the buy you'll probably want to do first to seed the curve).
* A square image for your token icon (PNG / JPG / GIF / WebP, ≤ 5 MB).

That's it. **No protocol fee on launch.** The 0.5 TON is pure gas — most of it is reserved by the contract for the curve's own initialization.

## The form

| Field           | Required | Notes                                                                             |
| --------------- | -------- | --------------------------------------------------------------------------------- |
| **Name**        | yes      | Up to 64 chars. Shown everywhere as the token's display name.                     |
| **Ticker**      | yes      | Up to 16 chars, letters + digits only (sanitized as you type).                    |
| **Description** | no       | One-liner that shows on the token's page.                                         |
| **Image**       | yes      | The token's icon. Drop a file or click to pick.                                   |
| **Website**     | no       | Bare domains OK (`tonton.fun`) — `https://` is added automatically.               |
| **Twitter / X** | no       | `@handle`, `x.com/handle`, or full URL — canonicalized to `https://x.com/handle`. |
| **Telegram**    | no       | `@handle`, `t.me/handle`, or full URL — canonicalized to `https://t.me/handle`.   |

## What happens after you sign

The launch flow runs through five steps (you'll see them as a stepper while it's running):

{% stepper %}
{% step %}

### Pin image

Your image is uploaded to IPFS via Pinata.
{% endstep %}

{% step %}

### Pin metadata

The TEP-64 metadata JSON (name, symbol, image URL, socials) is pinned.
{% endstep %}

{% step %}

### Sign tx

Your wallet pops up with the launch tx. The body carries only the metadata URI; the deployed factory reads everything else (treasury, STON.fi router, pTON wallet) from its own state.
{% endstep %}

{% step %}

### Confirm on-chain

The page polls the indexer for the new curve.
{% endstep %}

{% step %}

### Done

You're shown the new curve address with a copy button, a tonviewer link, and a button to open the token's page directly.
{% endstep %}
{% endstepper %}

The curve is deterministic — its address is computable from `(your_wallet, content_cell)` *before* the tx lands. The SDK exposes `getCurveAddress(client, factory, creator, content)` so you can preview the URL ahead of time.

## What you get

* A jetton master (the TEP-74 contract that issues your tokens) at a deterministic address.
* A bonding curve contract that issues jettons against TON spend (the 800M curve allocation).
* 200M jettons set aside in the curve, untouched, waiting for graduation.
* A creator address on the curve set to your wallet — you'll earn **0.30%** of every trade volume forever (or until graduation).

## Creator fees

Every buy and sell pays 0.30 % to the curve's creator. The fee accrues to the curve and is paid out to the creator wallet as part of each trade's outbound messages. There's no manual "claim" — it lands in your wallet automatically.

After graduation, the curve closes and creator fees stop. The token then trades on STON.fi as a standard pair, and standard STON.fi LP economics apply.

## Tips

* **Buy your own token after launch.** A token with zero buys looks dead. Doing a 0.5–1 TON self-buy seeds the curve, makes it appear in the Bonding column, and shows real volume.
* **The image is the first impression.** Square, high-contrast, readable at thumbnail size.
* **Tickers are case-sensitive on display but uppercased universally** — `Tonton` and `TONTON` show identically in most UI surfaces.
* **You can't undo a launch.** The factory deploys are immutable. Triple-check name, ticker, image before signing.


---

# Agent Instructions: 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:

```
GET https://docs.tonton.fun/launching-a-token.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.