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

# Quickstart

Install the SDK, connect a wallet and complete your first token purchase.

Use the stable production SDK and Arc Mainnet (`5042`). Import Classic APIs from the package root.

### Install

Use Node.js 20 or newer and viem 2.45 or newer, below 3.

```sh
pnpm add @masterpeach/launchpad-sdk@1.0.0 viem@^2.45.0
```

### Connect

This browser example creates a read client. Use your configured Arc Mainnet RPC endpoint and require chain ID `5042`.

```ts
import { createPublicClient, http } from "viem";
import {
  arcMainnetLaunchpadDeployment,
  createLaunchpadFactoryClient,
  defineLaunchpadChain,
  verifyLaunchpadDeployment,
} from "@masterpeach/launchpad-sdk";

const deployment = arcMainnetLaunchpadDeployment;
const rpcUrl = "https://rpc.arc-scan.org";
const publicClient = createPublicClient({ transport: http(rpcUrl) });
if (await publicClient.getChainId() !== deployment.chainId) {
  throw new Error("Use Arc Mainnet");
}
const chain = defineLaunchpadChain({
  slug: "arc-mainnet", chainId: deployment.chainId, family: "evm",
  nativeCurrency: { symbol: "USDC", decimals: 18 },
  rpcUrls: [rpcUrl], explorerUrl: "https://arc-scan.org",
  apiBaseUrl: window.location.origin, realtimeUrl: rpcUrl,
  deployment, quoteTokens: deployment.economics.quoteTokens,
  capabilities: { create: true, bondingTrade: true, partnerAttribution: true },
  confirmations: 2,
});
await verifyLaunchpadDeployment(publicClient, deployment);
const client = createLaunchpadFactoryClient({ publicClient, chain });
```

SDK 1.0.0 requires API and realtime URL metadata; this example uses RPC reads and starts no subscriptions. Verification checks deployment identity, bindings and pinned configuration. If it fails, check the reported difference against the approved production configuration before continuing.

### Prepare and confirm

For writes, also pass the connected `walletClient` to `createLaunchpadFactoryClient`. Check its account and chain before preparing an operation.

Read current fees and economics, obtain user confirmation, approve the correct spender and wait for approval receipts. Prepare the operation, send it through the wallet and confirm the receipt. An approval or simulation does not establish a completed launch or trade.

For ordinary creation, use `client.prepareLaunchAndBuy`; for optional Holder Fee Sharing, use `client.prepareLaunchWithHolderFeeSharing`. See [Token Creation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-creation) and the [production addresses](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/contract-address).


---

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