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

# Integration Checklist

Verify network setup, transaction protection and the features your application uses.

*

&#x20;  \* \[ ] Use `@masterpeach/launchpad-sdk@1.0.0`, its root import and `arcMainnetLaunchpadDeployment` on chain `5042`.

* [ ] Check production Factory, Forwarder and Holder Factory bindings with the matching ABIs.
* [ ] Read the creator's launch gate, current economics, fees and USDC allowlist.
* [ ] Confirm Creator Tax, Core buyback choice, first-buy amount, output limit and deadline.
* [ ] Approve the actual entry and confirm approval receipts before preparation.
* [ ] Use `prepareLaunchWithHolderFeeSharing` and a zero recipient placeholder for optional Holder sharing.
* [ ] Resolve the registered Holder with `getLaunchpadHolderBinding` before displaying rewards or preparing claims.
* [ ] Confirm actual fills/refunds and distinguish Curve closed, Swept and PoolCreated.
* [ ] Keep accrued fees, Escrow credits, collected Holder funds and wallet claims separate.
* [ ] Use the on-chain Epoch number, beneficiary, raw amounts and proof for Holder claims.
* [ ] Resolve pending transaction hashes before retrying and refresh state after confirmed receipts.


---

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