> 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** for launches made by script through a TokenFactory. **Not offered on the launch form.**

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

The **Launch** tab does not do this. A launch from `/launch` goes through the CurveLauncher, which mints the whole supply onto the bonding curve and creates no vesting wallet. When a launch starts from a token design that declares team vesting, the form says so: the schedule stays a published commitment in the design and is not applied on-chain. See [Enforced versus stated](/token-track-ideation/enforced-vs-stated.md).

Tokens that were launched with vesting show a vesting card on [the token page](/token-launch/token-page.md).

## Parameters (contract path)

| 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)
* [Deploy paths](/token-launch/deploy-paths.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.canhav.com/token-launch/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.