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

# Buyback & Vesting

Read vesting balances and release tokens with an authorized recipient wallet.

Read vesting balances and release tokens with an authorized recipient wallet.

**Read the vesting balance**

Buyback deposits lock purchased tokens in BuybackVault. Read the current schedule and releasable amount before offering a release.

```ts
const vest = await client.getBuybackVest(token);
const releasable = await client.getBuybackReleasable(token);
```

**Release vested tokens**

Only the vesting record’s `creatorRecipient` or `protocolRecipient` can trigger a release. Connect one of these wallets before submitting. The release credits both recipients’ shares to FeeEscrow.

```ts
// Connect vest.creatorRecipient or vest.protocolRecipient before submitting.
if (releasable > 0n) {
  const release = await client.prepareBuybackRelease(token);
  const releaseHash = await client.send(release);
  const result = await client.wait(releaseHash, { confirmations: chain.confirmations });
  if (result.status !== "confirmed") throw new Error("Release reverted");
}
const updatedVest = await client.getBuybackVest(token);
```

Each recipient then calls `client.prepareClaim({ asset: token })` from their own wallet to withdraw the credited tokens; see Fees & Claims.

**Understand the schedule**

Buyback deposits share one five-year weighted vesting schedule. New deposits can extend `vestingEnd` for the remaining balance. Display the current schedule and releasable amount; future deposits can change the end date.

A new lock can start after the previous vesting period ends, even if vested tokens remain unclaimed.

The current creator fee recipient can enable or disable buyback with `prepareSetBuybackEnabled`.

#### Hook buyback funding

Post-graduation buyback budgets originate in the creator portion of the Hook Fee. Creator Tax is credited to the creator separately. See [Hook fee allocation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/hook-behavior-and-fees) and [Fee settlement and state](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/fee-settlement-and-state) for conversion, partial buybacks and residual pending balances.

#### Direct contract calls

SDK equivalents: the vesting readers and prepareBuybackRelease. release credits FeeEscrow before a separate claim transfers tokens to a wallet.

* `BuybackVault.vest(address token) → LaunchVest` and `releasable(address token) → uint256`: vesting recipients, schedule and available tokens. `release(address token) → (uint256 creatorAmount, uint256 protocolAmount)` may be called by the recorded creator or protocol recipient. It credits FeeEscrow; recipients then call `claimToken(launchToken)`.

`Factory.transferCreatorFeeRecipient(address token, address newRecipient)` requires the **current fee recipient**. `Factory.setTokenBuybackEnabled(address token, bool enabled)` also uses the current recipient; the owner additionally has a disable-only path. Original creation alone does not retain these permissions after a recipient transfer. For Holder sharing, the recipient is the distributor contract.

#### Buyback tokens for Holder Fee Sharing

When the Creator Fee Recipient is the registered Holder Distributor, `client.prepareHolderHarvest` collects available vested project tokens and fee credits into that Distributor. A published Epoch and proof are still required before holders can 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-classic/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.
