> 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-pro/overview.md).

# Overview

Launchpad Pro manages a token from creation through bonding-curve trading to Uniswap V4 liquidity. Each token has its own curve and a configured ERC20 payment asset, called its **quote token**.

### The lifecycle

<table><thead><tr><th width="182.89453125">Stage</th><th>What happens</th><th>What your application does next</th></tr></thead><tbody><tr><td>Create</td><td>Deploy a token and its curve, with an optional initial buy</td><td>Confirm the receipt and read the launch state</td></tr><tr><td>Trade on the curve</td><td>Users buy with the quote token or sell launch tokens</td><td>Quote the trade, show fees and enforce the user's limits</td></tr><tr><td>Sweep</td><td>Once sellable tokens run out, the curve closes and its trading reserves move to the GraduationCoordinator</td><td>Confirm <code>Swept</code>; create the V4 pool</td></tr><tr><td>Trade on V4</td><td>Successful pool creation records <code>PoolCreated</code></td><td>Use the official pool through a compatible router</td></tr><tr><td>Recover if needed</td><td>A launch that remains <code>Swept</code> can become eligible for emergency exit</td><td>Follow the timed redemption flow</td></tr></tbody></table>

The last buy can trigger the sweep, including an initial buy during creation. If the sweep fails, the purchase can still succeed and the curve can already be closed. **A successful buy or 100% progress does not mean the V4 pool exists.** See [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation) for states, callers and retries.

Creators may choose `protectionDays=0` to turn pool protection off, or an integer from 1 to 365 days. The platform supplies the rules; the Creator selects the duration. With the current empty rules, no transfers are restricted.

### What users pay

Creating a token can require a creation fee, an optional initial purchase and network gas. Trades can include a base fee, Creator Tax and, for eligible early curve buys, Snipe Tax. Actual spending can be lower than the requested input on the last curve buy.

See [Fees & Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims) for the cost table and a worked revenue example.

### Where revenue goes

Trading fees are allocated between the platform, Creator revenue and any eligible Partner. Creator Tax belongs to Creator revenue. Partner commission comes from the platform's base-fee share; it is not an extra charge to the trader.

Choose how to receive Creator revenue:

* **Direct recipient:** fees are credited to the configured address in FeeEscrow, where that address can claim them.
* **Revenue distribution:** a Splitter allocates Creator revenue to configured recipients or supported strategies. The Splitter must collect revenue before recipients can claim; a strategy allocation is not itself a wallet payout.

Choose direct creation or [creation with revenue distribution](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/revenue-distribution).

### Network

Use **Arc Testnet, chain ID `5042002`**, with the SDK deployment presets and matching [contract addresses](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/contract-address).


---

# 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-pro/overview.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.
