> 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/buyback-and-vesting.md).

# Buyback and Vesting

Buyback is an optional Revenue Distribution strategy. It receives a share of Creator revenue, purchases project tokens and either vests or burns them. Allocation, funding, execution and payout are separate stages.

<table><thead><tr><th width="130.09765625">Strategy</th><th>Purchased tokens</th></tr></thead><tbody><tr><td><code>BUYBACK_VEST</code></td><td>Enter vesting for the configured Creator payee and/or Holder side</td></tr><tr><td><code>BUYBACK_BURN</code></td><td>Are burned; no wallet receives the burned tokens</td></tr></tbody></table>

Both strategy types are registered for the Pro deployment. They are separate from Classic's Core BuybackVault. Each Splitter composition can contain only one buyback strategy, including if that strategy's share later becomes zero.

### Follow the funds

1. Creator fees settle into FeeEscrow and the Splitter allocates the strategy's share.
2. Collection funds the strategy's Quote reserve.
3. A separate execution transaction buys tokens, applying its output limits.
4. Vest proceeds unlock for the configured payee or are delivered to a Holder budget; Burn proceeds are destroyed.

Outer Splitter weights determine how much revenue reaches buyback. Inner Creator/Holder Vest weights determine where purchased tokens go and are fixed from the creation table. A strategy reserve is not a wallet-claimable balance.

### Queries and claims

Use `getLaunchpadProBuybackState` for the reserve, current schedule, Creator payee, unlocked Creator amount and Holder-deliverable amount. Read actual state before offering a claim.

* `prepareLaunchpadProBuybackCreatorClaim` pays unlocked tokens to the configured Creator payee.
* `prepareLaunchpadProBuybackHolderDelivery` delivers unlocked project tokens to the Holder budget. Holders still need a published Epoch and proof.
* `prepareLaunchpadProBuybackEmergencyQuoteSettlement` handles remaining Quote under emergency rules, separately from vested-token claims.

These helpers do not execute a buyback. Send the prepared action, confirm its receipt and refresh balances. See [Holder Rewards](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/holder-rewards) for the final wallet claim.


---

# 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/buyback-and-vesting.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.
