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

# Integration Checklist

Check the flows your application enables before offering them to users.

### Connect and create

* [ ] Use the correct network, Factory and matching ABI.
* [ ] Default protection to zero and validate integer days from 0 to 365.
* [ ] Explain the current empty rules and include the nonzero ConfigRegistry hash even for zero days.
* [ ] Preview the final creation request for the account that will submit it.
* [ ] Show the creation fee, optional first-buy amount and network gas separately.
* [ ] Approve each asset to the correct spender and confirm approvals.
* [ ] Apply the initial-buy cap to Token output, and account for the initial recipient's Snipe Tax exemption.
* [ ] Confirm the creation receipt and read the resulting launch state.

### Trade and graduate

* [ ] Show the full fee-aware trade result with a minimum output or maximum input and deadline.
* [ ] Read opening tax for the actual token recipient; sells do not pay Snipe Tax.
* [ ] Test last-buy partial spending, refund and proportional minimum-output protection.
* [ ] Distinguish sold out, `Swept` and `PoolCreated`; retry the correct step after failure.
* [ ] Confirm the official V4 pool, active Hook and router support before offering swaps.
* [ ] Include the Hook fee in final router limits for both trade directions and Exact Input/Output.

### Settle and claim revenue

* [ ] Separate accrued fees, Escrow credits and wallet claimable amounts by asset.
* [ ] Avoid adding `pendingCreatorTax` to `pendingCreator` a second time.
* [ ] Show the configured Creator Fee Recipient and confirm each claim receipt.

### Recover and confirm

* [ ] Resolve pending transaction hashes before retrying; confirm every successful receipt.
* [ ] Preserve the user's agreed fee, price and slippage limits during recovery.
* [ ] Test emergency eligibility from `sweptAt` and redemption through the correct instance.
* [ ] Refresh state after writes and handle chain reorganizations in indexed history.

Use [Fees & Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims) for costs and [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation) for the state-transition table.

### Holder rewards

* [ ] Read `minHoldingFloor` and scale the threshold to 18-decimal project token units.
* [ ] Offer Meme or Quote mode; gate Custom on whitelist and converter/operator readiness.
* [ ] Use the API's Holder address, `onchainEpochId` and `claimFunction`; map Pro `quoteAmount` to SDK `dividendAmount`.
* [ ] Confirm funding, publication and wallet claims as separate stages.


---

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