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

# Core Features

Choose a guide for token launches, trading, fees or application integration.

Start with [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/quickstart), then choose the flows your application supports.

### Create and trade

* [Token Creation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-creation) — parameters, initial buy and Holder Fee Sharing.
* [Approvals](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/approvals) — assets, amounts and spenders.
* [Token Information](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-information) — registered contracts and project data.
* [Bonding Curve Trading](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/bonding-curve-trading) — quotes, buys, sells and refunds.
* [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/graduation) — sweep and V4 pool creation.
* [Trading Before and After Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/trading-before-and-after-graduation) — route selection.
* [Uniswap V4 Hooks](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks) — pool structure and swap fees.

### Revenue and recovery

* [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/fees-and-claims) — Escrow and Holder balances.
* [Partners](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/partners) — trade attribution and Partner fees.
* [Buyback and Vesting](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/buyback-and-vesting) — Classic Core buyback and release.
* [Emergency Exit](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/emergency-exit) — eligibility and redemption.

### Integration checks

* [Events and Indexing](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/events-and-indexing) — receipts, emitters and history.
* [Error Handling](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/error-handling) — failure handling and retries.
* [Integration Checklist](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/integration-checklist) — review enabled flows.

SDK preparation returns an unsent transaction. Confirm its receipt before showing success and read actual state after every lifecycle change.


---

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