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

# Overview

How Arc Launchpad takes tokens from bonding-curve trading to Uniswap V4 liquidity.

Launchpad Classic manages production Launchpad tokens on Arc Mainnet (`5042`), from creation and Curve trading to Uniswap V4 liquidity. Use the stable SDK `@masterpeach/launchpad-sdk@1.0.0` from its package root.

### Lifecycle

Create a token, trade on its Curve, sweep graduation reserves, then create the official V4 pool. A final buy can trigger the sweep; pool creation is a separate transaction. Read confirmed state before choosing the next action.

The [Arc Aggregator](https://docs.peach.ag/documentation/arc/aggregator/overview) can route supported trades when the pool is indexed and executable liquidity is available.

### Revenue

Creator revenue can go to a direct recipient or a registered Holder Distributor. Holder Fee Sharing collects revenue and vested Core buyback tokens for published reward periods. Fees accrued, funds collected and wallet claims are separate amounts.

### Start integrating

Follow [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/quickstart), confirm the [production addresses](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/contract-address), then use [Token Creation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-creation) and [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/fees-and-claims) for the flows your application supports.


---

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