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

# Launch a token

Anyone can launch a token from the Create page at [polypad.family/create](https://polypad.family/create). The call is permissionless: there is no allowlist and no backend signature. The wallet that sends the transaction becomes the launch creator.

## Before you start

* A wallet connected to Robinhood Chain with ETH for gas. See [Wallet and network](https://polydash.gitbook.io/polydash-docs/getting-started/wallet-and-network.md).
* A logo (HTTPS or IPFS URL, or the site's upload), a description, and any social links.
* A decision on the creator fee, the commitment window, and whether to make a dev buy.

## Steps

{% stepper %}
{% step %}

### Describe the token

Enter a name, ticker, logo, description, and up to 10 links. A public GitHub repository link is shown on the token page as the Build link. See [Build activity link](https://polydash.gitbook.io/polydash-docs/polypad/build-activity.md).
{% endstep %}

{% step %}

### Set the creator fee

Choose 0% to 5%. `0` means 0%, not a default. The fee is fixed for the life of the token and also applies after graduation. The Create page defaults to 1%.
{% endstep %}

{% step %}

### Pick the timing

Choose to open trading immediately, or open a commitment window before trading. See [Commitment window](https://polydash.gitbook.io/polydash-docs/polypad/commitment-window.md).
{% endstep %}

{% step %}

### Optional: dev buy

A creator can buy at launch. The ETH attached to the transaction must equal the dev buy amount. In a commitment launch, the dev buy runs before commitments are filled.
{% endstep %}

{% step %}

### Sign the transaction

Review the transaction in your wallet and sign. The factory deploys the token and a clone of the launch contract, and emits `LaunchCreated` with the new addresses.
{% endstep %}
{% endstepper %}

## Parameters and limits

| Field                 | Rule                                                                                     |
| --------------------- | ---------------------------------------------------------------------------------------- |
| `name`, `symbol`      | Required. The API caps them at 64 and 32 UTF-8 bytes                                     |
| `imageUri`            | Empty, or an `https://` or `ipfs://` URL                                                 |
| `description`         | Optional. The API caps it at 2,000 characters                                            |
| `socialLinks`         | At most 10                                                                               |
| `creatorFeeBps`       | 0 to 500 on the current factory (0% to 5%)                                               |
| `creatorPayoutWallet` | Zero address means the creator. Creator fees only go to this address                     |
| `devBuyEth`           | Optional, in wei. Must equal the ETH sent                                                |
| `totalSupply`         | `0` selects 1,000,000,000 tokens. Otherwise 1,000,000 to 1,000,000,000,000 tokens        |
| `virtualEthReserve`   | `0` selects 1.5 ETH. Otherwise 0.01 ETH to 1,000 ETH                                     |
| `launchDelay`         | Seconds before trading opens. `0` opens immediately. Maximum 30 days (2,592,000 seconds) |

There is no launch fee. Trades pay a 0.2% platform fee plus the creator fee. Anti-sniper settings are copied from the factory when the launch is created. See [Fees](https://polydash.gitbook.io/polydash-docs/polypad/fees.md).

## What the token contract does

The whole supply is minted once to the launch contract. The token has no owner, mint, pause, blacklist, or transfer tax. After you launch, the token is a normal ERC-20 that anyone can trade on the curve.

## After launch

* Add [creator vesting](https://polydash.gitbook.io/polydash-docs/polypad/creator-vesting.md) or a [creator bond](https://polydash.gitbook.io/polydash-docs/polypad/creator-bond.md) to earn Holder Protections labels.
* Open a [staking pool](https://polydash.gitbook.io/polydash-docs/polypad/staking-pools.md) for holders.
* Claim [creator fees](https://polydash.gitbook.io/polydash-docs/polypad/creator-fees.md) at any time.

## Risks

Launching is permissionless and irreversible. You are responsible for what you launch: no impersonation, no trademark abuse, no misleading claims. A listing on Polypad does not mean Polydash reviewed the token. The contracts are **Not audited.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://polydash.gitbook.io/polydash-docs/polypad/launch-a-token.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
