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

# Creator vesting

Creator vesting locks a creator's token allocation on a cliff and a linear schedule, so holders can see that the allocation cannot be dumped at once.

## Who it is for

Creators of Polypad tokens who want a public, enforced lock on their own allocation, and holders who want to check it.

## How it works

`CreatorVestingFactory` creates one `CreatorVestingVault` per allocation. Tokens move straight from the depositor into the vault and vest linearly after a cliff.

{% stepper %}
{% step %}

### Create a vault

The depositor chooses a beneficiary, an amount, a cliff, and a duration. Only tokens launched through Polypad are accepted.
{% endstep %}

{% step %}

### Wait for the cliff

Nothing is releasable before the cliff ends.
{% endstep %}

{% step %}

### Release

After the cliff, tokens vest linearly. Anyone can call release. Funds only ever move to the beneficiary.
{% endstep %}
{% endstepper %}

## Key properties

* **Ownerless.** No admin withdraw and no pause.
* The beneficiary can only lengthen the cliff or duration, never shorten them.
* Beneficiary transfer is two-step (`proposeBeneficiary`, then `acceptBeneficiary`), and only the current beneficiary can start it.
* **Optional staking.** The vault can stake locked tokens in a V2 staking pool. Rewards go to the beneficiary right away and are not on the vesting schedule. Anyone can call `claimRewards()`, and rewards are paid minus the pool's claim fee.
* Views for integrations include `vestedAmount`, `lockedAmount`, `releasable`, and `meetsBadgeMinimum`.

## Holder Protections label

`meetsBadgeMinimum()` returns true only when the cliff is at least **30 days** and the duration is at least **180 days**. The contract accepts shorter schedules. The function is a label for interfaces. See [Holder Protections](https://polydash.gitbook.io/polydash-docs/polypad/holder-protections.md).

## Contract

CreatorVestingFactory: [`0xbbF618395E6C7ac0E9AC6dBEC26BA8cd160d7022`](https://robinhoodchain.blockscout.com/address/0xbbF618395E6C7ac0E9AC6dBEC26BA8cd160d7022) (Sourcify exact match)

## Risks

A vault locks one allocation. It does not lock other wallets and does not keep a price. The contracts are **Not audited.**


---

# 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://polydash.gitbook.io/polydash-docs/polypad/creator-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.
