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

# Core Features

Start with [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/quickstart) and use [Tax and Pool Protection](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/tax-and-pool-protection) for creation and protection details.

### Create and trade

* [Token Creation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/token-creation) — creation, fees and first buy.
* [Approvals](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/approvals) — the asset and spender for each operation.
* [Token Information](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/token-information) — launch data, metadata and project roles.
* [Bonding Curve Trading](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/bonding-curve-trading) — buys, sells, fees and refunds.
* [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation) — states, pool creation and recovery.
* [Trading before and after graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/trading-before-and-after-graduation) — choose the available trading route.
* [Uniswap V4 Hooks](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks) — official pools, swap fees and Partner data.

### Costs, revenue and recovery

* [Fees & Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims) — what users pay, how fees split and when they can be claimed.
* [Partners](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/partners) — attribution and Partner payouts.
* [Revenue Distribution](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/revenue-distribution) — recipient allocations and claims.
* [Holder Rewards](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/holder-rewards) — funded rewards and claims.
* [Buyback & Vesting](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/buyback-and-vesting) — strategy availability and flow.
* [Emergency Exit](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/emergency-exit) — eligibility and token redemption.

### Build your integration

* [Events & Indexing](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/events-and-indexing) — confirm results and track actual funds.
* [Error Handling](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/error-handling) — recover without changing the user's agreed limits.
* [Integration Checklist](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/integration-checklist) — verify the flows enabled in your application.

Confirm a successful transaction receipt before treating an action as complete.


---

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