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

# Partners

Partners earn a configured share of the platform's base trading-fee revenue. Each `bytes32 partnerId` belongs to its PartnerRegistry deployment.

## Attribute a trade

Pass the ID as the fifth argument of the Curve's buy/sell overload. On V4, pass it through `hookData`; see [Partner and HookData](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks/partner-and-hookdata).

Zero means no Partner. An unknown nonzero ID is rejected. An existing Partner earns new commission when `commissionEnabled=true` and `frozen=false`.

## How commission is calculated

The launch's `protocolFeeShareBps` determines the platform portion of the base fee. The Partner's `shareOfPlatformBps` is applied to that portion. This commission is included in the trade's existing fee; it is not another surcharge.

Partner commission excludes Curve Snipe Tax and all Creator Tax. See the [100 Quote allocation example](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims#illustrative-100-quote-buy).

## Status and roles

<table><thead><tr><th>Status</th><th width="135.296875">New commission</th><th>Settle existing revenue into Escrow</th><th>Claim / Partner management</th></tr></thead><tbody><tr><td>Commission enabled, unfrozen</td><td>Yes</td><td>Allowed</td><td>Allowed for the authorized role</td></tr><tr><td>Commission disabled, unfrozen</td><td>No</td><td>Allowed</td><td>Allowed for the authorized role</td></tr><tr><td>Frozen</td><td>No</td><td>Allowed</td><td>Blocked</td></tr></tbody></table>

Registry Owner manages Partner creation, name, commission share and status. The Partner Controller can change its Recipient and propose/cancel a Controller transfer while unfrozen; the proposed Controller must accept. The Recipient is authorized to claim. These roles are separate from the token's Creator Controller and Creator Fee Recipient.

## Receive commission

Accrued Curve or Hook commission must first be settled into FeeEscrow. Read `partnerBalance(partnerId, asset)`, then claim with `claimPartner(partnerId, asset)` or a valid batch entry. The caller must be the current Recipient and the Partner must be unfrozen.

Balances are keyed by Partner ID and fee asset. After a valid Recipient change, the new Recipient can claim the Partner's historical unclaimed balances. Disabling commission does not erase them. See [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims) for claim methods.


---

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