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

# Holder Rewards

Holder Rewards allocate part of Creator revenue to eligible token holders. Funding a Holder, publishing a reward period and a wallet claiming are separate steps.

### Configure rewards

Creators select the fee dividend asset and minimum holding when adding a `HOLDER` entry to [Revenue Distribution](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/revenue-distribution).

<table><thead><tr><th width="105.7890625">Mode</th><th>Fee dividend asset</th><th>Input</th></tr></thead><tbody><tr><td><code>meme</code></td><td>This project's token</td><td><code>minHolding</code></td></tr><tr><td><code>quote</code></td><td>This project's Quote asset</td><td><code>minHolding</code></td></tr><tr><td><code>custom</code></td><td>An approved asset</td><td><code>minHolding</code> and <code>dividendToken</code></td></tr></tbody></table>

Read `getLaunchpadProHolderSettings(pro)` before showing the form. `minHolding` uses the project's 18-decimal token units and must meet the current `minHoldingFloor`. The configured floor is 10,000 tokens (`10000000000000000000000` raw units). Existing projects use their Holder's own `minHolding()`.

Use `encodeLaunchpadProHolderConfiguration({ mode: "quote", minHolding })` for the Holder entry's initialization. Meme and Quote resolve their asset on-chain. Custom requires an approved token and configured converter/operator; it is currently unavailable because those conversion components are unset. Enable it only when the SDK settings report `customEnabled` for the selected asset.

Fees already in the chosen asset can fund the dividend budget. Other assets remain pending conversion. Buyback Vest tokens remain project tokens and can be included as the separate token amount in the same claim.

### Add Holder after creation

For a project with a Splitter but no Holder, the Splitter's authorized creator (`creatorAuthority()`) can add a Holder before emergency exit. Read Splitter `configurationVersion()`, build the Holder entry and use `previewLaunchpadProStrategies(pro, token, expectedVersion, { entries })`. Review and submit `prepareLaunchpadProStrategies` with the same inputs. This calls the **Composition Creator**, not the Core Factory. Confirm the receipt and resolve the Holder from the Distributor Factory.

### From revenue to a wallet

1. Curve or Hook fees settle into FeeEscrow.
2. The Splitter and Holder collect revenue into the available reward budget.
3. An authorized publisher creates an on-chain Epoch backed by that budget.
4. The application obtains the beneficiary's proof and prepares a claim.

A receivable, funded budget or published Epoch is not a wallet payment. Read the current state and keep amounts separate by asset.

### Query and claim

```http
GET https://api-arc.cipheron.org/distributor/v1/accounts/{account}/allocations?chainId=5042002&token={projectToken}&includeProof=true
```

Use the record's Holder address (`distributor`), **`onchainEpochId`**, beneficiary and proof. Epoch `0` is valid. Do not use the API's database ID as an on-chain Epoch number.

For Pro `claimDividend`, API `quoteAmount` means the selected `dividendToken` amount; `coinAmount` means project tokens released by Buyback Vest. Map `quoteAmount` to the SDK claim's `dividendAmount`. Use `prepareLaunchpadProHolderDividendClaim(pro, { token, splitter, dividendToken, claim })`; its preflight checks the bound instance, Epoch asset, expiry and proof before simulation.

Enable claiming only when the period is published, unclaimed, not rolled over and within its claim deadline, with a usable proof. Use the record's `claimFunction` and matching Epoch ABI. Submit the prepared transaction, confirm the receipt and refresh claimed state. Claims pay the beneficiary, require network gas and need no ERC20 approval.


---

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