# Create A Token

## Fixed parameters

Every token created on Bound Launchpad has these fixed values:

| Parameter                 | Value                                                        |
| ------------------------- | ------------------------------------------------------------ |
| Total supply              | 1,000,000,000 tokens                                         |
| Liquidity pool allocation | 20% of supply                                                |
| Premine                   | 100% (directed to Bound-controlled wallets for distribution) |
| Decimals                  | 2                                                            |
| Tokens per mint           | 10,000                                                       |

## Flexible parameters

You choose:

* **Display ticker** - A short nickname used in the Bound UI (not stored on-chain)
* **Rune ticker** - The official on-chain ticker
* **Token image** - Visual identity for your token
* **Symbol** - e.g. 😂
* **Description** - What your token is about
* **Socials** - Twitter, Telegram, Website (optional)

## Timing

After submitting your etch transaction:

1. Wait for **6 Bitcoin block confirmations** - required by the Runes protocol to prevent front-running
2. After reveal, wait **1 more block** confirmation
3. Your token is now open for minting

## Cheap etch option

The **Cheap etch** switch is on by default. It restricts image size so your etching transaction costs no more than $30. Turn it off if you want to submit a larger image.

{% hint style="info" %}
**VERIFY** - Team token vesting terms to be confirmed with team.
{% endhint %}


---

# 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://bound-1.gitbook.io/bound-docs/launchpad/create-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.