> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperpad.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# Vesting

> Drip buyer allocations, and the team's too.

HyperPad has **two independent** vesting systems. They're easy to mix up, so here's the clean split.

## Buyer vesting

Controls how the tokens **buyers** purchased unlock after the sale.

| Field             | Meaning                                          |
| ----------------- | ------------------------------------------------ |
| `tgeBps`          | % unlocked immediately when claims open (0–100%) |
| `cliffDuration`   | Delay before any linear unlock begins            |
| `vestingDuration` | Linear unlock window after the cliff             |

The clock starts when **claims open** — i.e. when the LP is created and trading goes live (or at
finalize if there's no LP). Before the cliff, a buyer can claim only the TGE portion; after it, the
rest unlocks linearly. Leave it at **100% TGE** for a normal instant-claim launch.

<Info>
  Vested or not, buyer tokens are held in a segregated **claim vault** — separate from the raise — so
  there's no way for an unlock schedule to put your buyers' tokens at risk.
</Info>

## Team vesting

Vests **your** allocation (the team remainder) on its own schedule via a dedicated `TokenVesting`
wallet, with its own clock (independent of the sale, so a failed raise can't lock your tokens).

| Field             | Meaning                              |
| ----------------- | ------------------------------------ |
| `teamTgeBps`      | % of the remainder unlocked at start |
| `teamStart`       | Vesting origin (0 = launch)          |
| `teamCliff`       | Cliff in seconds                     |
| `teamVesting`     | Linear seconds after the cliff       |
| `teamBeneficiary` | Recipient (0 = you)                  |