> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-creation.md).

# Token Creation

Create a token, configure an optional initial buy and confirm the launch.

Create a production Classic token on Arc Mainnet with `LaunchpadCreateTokenParams`. Classic uses one `creatorTaxBps` rate and the Core `buybackEnabled` option.

### Review the request

Choose token metadata, approved USDC as the Quote asset, an enabled launch configuration, Creator fee settings, tax exemptions, an optional first buy, minimum output, deadline and salt. Read the creator's launch gate, current fees and economics before confirmation.

Supply a nonzero `expectedEconomics` calculated from the current Quote economics, launch configuration and fee policy with `launchpadEconomicsHash`. If those terms change, refresh the preview and obtain confirmation again.

Creation fees, the optional purchase and network gas are separate costs. Combine funding only when fee and Quote use the same asset.

### Choose the entry

| Flow                                    | SDK method                                         | Input spender           |
| --------------------------------------- | -------------------------------------------------- | ----------------------- |
| Ordinary creation through the Forwarder | `client.prepareLaunchAndBuy(params)`               | Current LaunchForwarder |
| Optional Holder Fee Sharing             | `client.prepareLaunchWithHolderFeeSharing(params)` | Current LaunchForwarder |
| Direct Factory creation                 | `client.prepareCreateToken(params)`                | Classic Factory         |

Use the production client from [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/quickstart). Approve the actual entry, confirm approval receipts, prepare the operation, send and wait for a successful receipt.

### Optional Holder Fee Sharing

Set `creatorFeeRecipient` to the zero-address placeholder. The production Holder-aware Forwarder creates and registers the per-launch Holder Distributor, installs it as the recipient and creates the token in one transaction. The SDK supplies the supported initialization data.

Use `prepared.preview.distributor` for the prediction, then confirm the deployed binding with `getLaunchpadHolderBinding`. Creator fees and vested Core buyback tokens must be collected and published in an Epoch before holders can claim; see [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/fees-and-claims).

### Continue from the confirmed state

Read the token and Curve addresses from the receipt. An initial buy can sell out the Curve and attempt a sweep. Read the [graduation state](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/graduation) before offering further trades or V4 pool creation; a successful creation does not by itself prove the V4 pool exists.


---

# 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://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-creation.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.
