> For the complete documentation index, see [llms.txt](https://docs.canhav.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.canhav.com/token-launch/vesting.md).

# Vesting

**Available now.**

Optional vesting can be created in the **same transaction** as the token launch. The factory deploys a vesting wallet clone and funds it with a percent of supply.

## Parameters (UI constraints)

| Parameter      | Range                                  |
| -------------- | -------------------------------------- |
| Vested percent | 1-100 (integer)                        |
| Duration       | 1-3650 days                            |
| Cliff          | 0 or more days; cannot exceed duration |

`startTimestamp == 0` in the contract path resolves to `block.timestamp`. The **resolved** start is what gets emitted in events.

## How addresses work

Vesting clone salt is derived from the **token address** (`keccak256(abi.encode(token))`), not from the launch user salt alone. That keeps vesting addresses collision-free even when a userSalt is reused across factory versions.

## Ownership and release

* The vesting **beneficiary is the Ownable owner** of the wallet (OpenZeppelin v5 pattern). Ownership can be transferred (including selling unvested positions). Always read live `owner()`, do not freeze the event's beneficiary forever.
* `release(token)` is **permissionless** and always pays the current owner.

## Events

* `TokenLaunched` is the same whether vesting is used or not.
* Vesting details live in a separate `VestingCreated` event.

## Related

* [Create a token](/token-launch/create-a-token.md)
* [Governance](/token-launch/governance.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.canhav.com/token-launch/vesting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.