> 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/fees-and-claims.md).

# Fees & Claims

Read pending and claimable fees, then withdraw credited balances.

Display trading fees, Creator revenue, Core buyback and network gas separately. Fees accrue in the Curve or Hook, then settlement credits FeeEscrow. Pending amounts are not yet wallet claimable.

### FeeEscrow claims

Read balances for the actual recipient and asset with `client.getClaimableBalance`. Use `client.prepareClaim({ asset })` for the connected recipient; omit `amount` to claim all, or supply a partial amount. Partner balances use `getPartnerClaimableBalance` and `preparePartnerClaim`.

FeeEscrow balances are per recipient and asset. Changing the Creator recipient does not move existing credits. Confirm the claim receipt and refresh the balance. Claims require gas and no ERC20 allowance.

### Holder Fee Sharing

Production Classic uses its registered Holder Distributor. Resolve it with `getLaunchpadHolderBinding({ publicClient, deployment }, token)` and require `binding.registered`. Use the production `arcMainnetLaunchpadDeployment` from [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/quickstart).

Revenue collection, Epoch publication and wallet payment are separate steps. `client.prepareHolderHarvest(distributor)` collects available Escrow revenue and vested Core buyback tokens; it does not publish an Epoch or pay holders. Publication requires the authorized publisher.

### Validate and claim

Obtain the beneficiary's allocation and Merkle proof from the project's production reward service. Construct a `LaunchpadHolderAllocation` with:

* `epochId`: the on-chain Epoch number as `bigint`; `0` is valid. Never use a service database ID.
* `account`: the beneficiary.
* `quoteAmount` and `coinAmount`: raw USDC and project-token amounts.
* `proof`: the Merkle proof for those exact amounts and beneficiary.

Read the Epoch and claimed/exclusion state using `client.getHolderEpoch`, `client.hasHolderClaimed` and `client.isHolderExcluded`. Require an existing, unexpired, non-rolled-over Epoch and validate the allocation against its root with `launchpadHolderAllocationMatchesRoot`.

Prepare `client.prepareHolderClaim({ distributor, allocation })`, send and confirm the receipt, then refresh the claimed state. Payment goes to `allocation.account`, including when another wallet pays gas. `prepareHolderClaimMany` supports claims against the same distributor; one invalid allocation reverts the batch.

See [Hook settlement](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/fee-settlement-and-state) for post-graduation fees and [Buyback and Vesting](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/buyback-and-vesting) for the Core flow.


---

# 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/fees-and-claims.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.
