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

# Contract Address

Production Classic contracts on Arc Mainnet (`5042`). Use `@masterpeach/launchpad-sdk@1.0.0` and `arcMainnetLaunchpadDeployment`.

#### Core integration contracts

* **LaunchFactory** — configuration, token discovery and `curveFor(token)` lookup.
* **LaunchForwarder** — token creation with an optional initial buy.
* **BondingCurve** — per-token quotes and trades before graduation.
* **FeeEscrow** — fee balances and claims.

Index **GraduationCoordinator** for graduation events and **MemeHook** for V4 fee events.

Use `verifyLaunchpadDeployment` to validate the deployment. Always check the current launch gate before creation.

#### Arc Mainnet Contract addresses

SDK `contractVersion`: `production-v2-arc-mainnet-v1`.

Chain ID: 5042. RPC: <https://rpc.arc-scan.org>. Use the Holder-aware LaunchForwarder and matching HolderDistributorFactory. Read the current launch gate before creation.

**Protocol contracts**

<table><thead><tr><th width="413.015625">Contract</th><th>Address</th></tr></thead><tbody><tr><td>LaunchFactory</td><td><code>0x7E462d220b6b0a4c55B205B613133dc1C1Cc9dC1</code></td></tr><tr><td>LaunchForwarder</td><td><code>0x7b9720bC177e8B6F96962e9b15891f27108cAd40</code></td></tr><tr><td>FeeEscrow</td><td><code>0x29Ad26C48267B791DC2f6A2D4f3Fd819E6301540</code></td></tr><tr><td>PartnerRegistry</td><td><code>0x65ED91aaC042496be1A0527949fe216c1Df362C5</code></td></tr><tr><td>BuybackVault</td><td><code>0x139271e6694B4047949cDD0D4343d116dc732113</code></td></tr><tr><td>MemeHook</td><td><code>0x173c4Bdd5CF95A935D2B5636C573C5F4DF062044</code></td></tr><tr><td>GraduationCoordinator</td><td><code>0xD25E4bdABb03437e430a31d9bFef547096a3E596</code></td></tr><tr><td>LaunchLocker</td><td><code>0x901f99bcb789AB929Fa7d580970A04dC555F7e13</code></td></tr><tr><td>LaunchDeployer</td><td><code>0xfC15d28188dF2a9dFCdc1031fF5e4A79dEE8547e</code></td></tr><tr><td>GraduationExecutor</td><td><code>0xBB5a660EC97548d9D83d938805F908f9d9d3a4d3</code></td></tr><tr><td>EmergencyDistributorFactory</td><td><code>0xde1af9c099406A65bc8de967998C29fbe93eB4Cb</code></td></tr><tr><td>OrphanedAssetsVault</td><td><code>0x1958553B580aF77F664f43eE062c5D33bc9357a9</code></td></tr></tbody></table>

OrphanedAssetsRecipient uses the same address as OrphanedAssetsVault.

**Holder Distributor components**

| Contract                        | Address                                      |
| ------------------------------- | -------------------------------------------- |
| HolderDistributorFactory        | `0x14177a906578CD3A5535d892D2929CF73097c547` |
| HolderDistributorBeacon         | `0x89945b6aF1eD7DFCFF6AcAf9EFc9cB6D4c585A79` |
| HolderDistributorImplementation | `0xfA4B04494d655E8314009e049BD82b0Fd3271d94` |

Use the current Holder-aware LaunchForwarder for frontend creation: `launchAndBuy(params)` for ordinary creation, or `launchWithHolderFeeSharing(params`,`distributorInitializationData)` for optional Holder Fee Sharing. Approve the current Forwarder for either call. Ordinary creation remains backward compatible. Holder mode creates a separate Distributor for each token.

**Uniswap V4 dependencies**

| Contract        | Address                                      |
| --------------- | -------------------------------------------- |
| PoolManager     | `0x8366a39CC670B4001A1121B8F6A443A643e40951` |
| PositionManager | `0x6049c9a0e26405C0985f9E3685C87d0aE917f82B` |
| Permit2         | `0x000000000022D473030F116dDEE9F6B43aC78BA3` |

**Quote token**

| Token             | Address                                      |
| ----------------- | -------------------------------------------- |
| USDC (6 decimals) | `0x3600000000000000000000000000000000000000` |


---

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