> ## Documentation Index
> Fetch the complete documentation index at: https://docs.o1.exchange/llms.txt
> Use this file to discover all available pages before exploring further.
# Allocations and vesting
> Distribute tokens at launch through immediate allocations or fixed staircase vesting without adding control to the token.
Allocations are optional and are deducted from the supply placed into the pool. They must be fully specified before the launch transaction is signed.
## Allocation types
The recipient receives the specified token amount in the launch transaction and can transfer it immediately.
The vesting contract receives the amount at launch and releases it to the beneficiary at the chosen milestones. No administrator can change the recipient or schedule later.
## Current caps
| Constraint | Limit |
| -------------------------------- | ------------------------------------- |
| Immediate plus vested recipients | 128 total |
| Vested beneficiaries | 64 |
| Steps per beneficiary | 24 |
| Vesting steps across the launch | 128 |
| First unlock | At least 1 day after launch |
| Final unlocked percentage | Exactly 100% |
| Total allocated amount | Strictly less than total token supply |
Recipient addresses must be valid and unique across both allocation types. Launch system contracts cannot be used as recipients.
## Pool coverage and discovery
Immediate and vested allocations reduce the number of tokens placed into permanent liquidity. o1 recommends leaving at least **25% of the fixed supply** in the pool for healthier market depth. This is a market-quality recommendation, not the contract minimum.
The create form and final review show the projected pool share before signing. Larger allocations can increase price impact and volatility, and very low pool coverage can make a launch ineligible for ranked discovery views such as Trending, Market Cap, or 24-hour Volume. New, search, the token page, and trading remain available. Ranked placement is never guaranteed.
## Staircase schedules
Each step contains:
* the number of days after launch;
* the percentage released at that step.
The interface accepts whole days and percentages with up to two decimal places. Step percentages must add up to 100%, and the preview shows both the newly released share and the cumulative amount available by each date.
For a 1,000,000 token allocation:
| Day | Newly unlocked | Total unlocked | Total tokens available |
| --: | -------------: | -------------: | ---------------------: |
| 30 | 20% | 20% | 200,000 |
| 90 | 30% | 50% | 500,000 |
| 180 | 50% | 100% | 1,000,000 |
Nothing streams between steps. At day 89, only the first 200,000 tokens are vested. At day 90, the cumulative vested amount becomes 500,000.
## Validation rules
For every schedule:
1. unlock dates must strictly increase;
2. every step must release a positive percentage;
3. step percentages must add up to exactly 100%;
4. rounded cumulative token amounts must strictly increase;
5. the first point must be at least one day after launch.
For very small allocations, each milestone must unlock at least some additional token amount. A step that rounds to the same amount as the previous step is rejected.
## Claims and guarantees
The vesting contract has no administrator. Nobody can withdraw locked tokens early, change a schedule, replace a beneficiary, or redirect a claim.
Anyone may trigger a claim, but the tokens always go to the beneficiary chosen at launch. The app shows the total allocation, amount already claimed, schedule, and amount available now.
For a larger claim campaign, an immediate allocation can fund a separately deployed and audited Merkle claim contract. See [Plan your launch](/launchpad/launch-planning#optional-airdrop-claim-tool).