> For the complete documentation index, see [llms.txt](https://bread-5.gitbook.io/bread/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bread-5.gitbook.io/bread/for-developers/how-to-launch-token.md).

# How to launch a token

### Who this section is for

bread.hot v.1 gives developers an environment where a token has a real chance to go through a high-quality start and build a stable holder base.

#### What you need

* A Solana wallet with SOL balance — token deployment is **free (0 SOL)**, you only need standard gas (\~0.000005 SOL)
* Token name and ticker
* Token image — square recommended, minimum 512×512
* Token description — 1–3 sentences (optional but recommended)
* Social links — Twitter / Telegram / Website (optional)

#### Steps

**1. Connect your wallet**

Click "Connect Wallet" in the top right corner.

**2. Open Create**

The "Create token" button in the header opens the deploy form.

**3. Fill in the token form**

* **Name** — display name of the token
* **Ticker** — 3–10 Latin characters
* **Image** — drag-and-drop or upload
* **Description** — what the token is about, in short
* **Social links** — Twitter, Telegram, Website (help early traders trust the token)

**4. Pick a launch mode**

* **Bonding Curve Launch** — instant curve-based trading from second one. Default choice. Fits viral moments and event-driven launches
* **Presale Launch** — same price for every participant, trading opens after 45 SOL is collected. Fits when you already have a community and symmetric entry matters

Not sure which one — see "How to choose a launch mode".

**5. Set launch parameters**

* **Max Buy** — per-wallet limit (Bonding Curve: step 0.1%, up to 2% of supply; Presale: 2 SOL per wallet)
* **Buy fee** — 1% for Bonding Curve
* Other parameters (target 45 SOL, sell tax 15%, Meteora migration) are fixed

**6. Sign the transaction**

Wallet popup → confirm. Token creation cost — **0 SOL**. The token goes live 1–2 seconds after signing.

**7. Share the link**

After confirmation the token starts trading. Copy the link from the address bar and post simultaneously across all channels — Telegram, Twitter, Discord. The earlier first holders show up, the stronger the momentum.

#### After launch

* The token starts trading on the bonding curve immediately. Price grows with every buy
* Max Buy is active — no wallet can take more than 2% of supply
* Pre-migration buys go through bread.hot only (direct-access-only) — external speed software has no edge
* When the curve collects 45 SOL — the token automatically migrates to Meteora DAMM

#### If the transaction fails

* **Insufficient balance** — top up the wallet with SOL (you only need gas, \~0.01 SOL is enough with margin)
* **Ticker already taken** — pick a unique ticker
* **Network congestion** — retry in a minute
* **Wallet rejected** — make sure you sign with the right wallet

### Strategic support from the team

If your community trusts you, but you don't trust the current market structure and you don't have a team — we are open to working directly with you and your people to build bigger projects and to support them from our side.

***


---

# 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://bread-5.gitbook.io/bread/for-developers/how-to-launch-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.