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

# Revenue Distribution

Revenue Distribution routes Creator revenue to a Splitter that allocates it among wallets and strategies. Protocol and Partner shares are deducted before this stage. A direct Creator Fee Recipient remains available when sharing is unnecessary.

### Connect

Use `publicClient` and `arcTestnetLaunchpadV2Deployment` from [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/quickstart):

```ts
import {
  arcTestnetProDistributionDeployment,
  createLaunchpadProClient,
  verifyLaunchpadProDistribution,
} from "@masterpeach/launchpad-sdk/v2";

const pro = createLaunchpadProClient({
  publicClient,
  deployment: arcTestnetLaunchpadV2Deployment,
  distribution: arcTestnetProDistributionDeployment,
});
await verifyLaunchpadProDistribution(pro);
```

For transactions, also pass the connected `walletClient`. Use the matching Core and Distributor presets together.

### Create with sharing

1. Build the V7 request, including `protectionDays`. Set `creatorFeeRecipient` to the zero-address placeholder; the Forwarder resolves the Splitter.
2. Build `{ entries }`. Each entry contains `recipient`, positive integer `shares`, `strategyType`, `initialization` and `metadataURI`. A direct wallet uses its address, `zeroHash` and `"0x"`; a strategy uses the matching strategy configuration.
3. Call `previewLaunchpadProRevenueLaunch`. Review its pinned request, addresses, allocations, protection choice and funding.
4. Approve required assets to the **Revenue Forwarder** and confirm approvals.
5. Use `prepareLaunchpadProRevenueLaunch`, send and confirm the receipt. Read the resulting composition and launch state.

The SDK encodes dynamic creation version 4 and forwards the selected protection days. Do not substitute a Classic request or manually reuse a different Forwarder.

### Allocate and claim

<table><thead><tr><th width="177.83203125">Stage</th><th>Meaning</th></tr></thead><tbody><tr><td>Accrued Core fees</td><td>Await Curve/Hook settlement</td></tr><tr><td>FeeEscrow credit</td><td>Creator revenue credited to the recipient or Splitter</td></tr><tr><td>Splitter allocation</td><td>Funds assigned to a wallet or strategy</td></tr><tr><td>Wallet claimable</td><td>Funds the wallet can withdraw through the applicable claim flow</td></tr></tbody></table>

For 100 raw units with weights 4:4:2, allocations are 40, 40 and 20. Each allocation rounds down independently; a rounding remainder is not automatically paid to the last recipient.

Use `getLaunchpadProRewardsState` to query by asset, `prepareLaunchpadProCollectAndHarvest` to prepare collection and `prepareLaunchpadProRevenueClaim` for direct-wallet allocations. Strategy allocations follow [Holder Rewards](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/holder-rewards) or [Buyback and Vesting](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/buyback-and-vesting). Allocation alone does not fund a published reward period or complete a buyback.

### Add sharing to an existing token

While recipient updates remain enabled, the current Creator Controller can prepare a candidate Splitter with `prepareLaunchpadProRevenueDistribution`, then activate it with `prepareLaunchpadProRevenueActivation`. Confirm both transactions. `getLaunchpadProRevenueComposition` distinguishes a prepared candidate from the active Creator Fee Recipient.

Keep the Splitter and Holder addresses with each allocation and claim. Changing a recipient does not move previously credited funds or published reward rights. Core control, Splitter authority, Vest payee and Holder publisher are separate roles.


---

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