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

# Vested Sale

PulseFinity offers vesting options for projects to ensure long term price stability by locking away the tokens of presale investors for a period of time. It prevents presale investors from selling all their tokens at once at listing time, which causes too much sell pressure and crashes the price. Projects will be able to select vesting options to their requirements. Projects should list their requirements as stated below:

GE Date: Should be the listing time. 

TGE (percent): The percentage of the first batch of team tokens to be released. Please note that this is expressed in percentage, not number of tokens. 

Cycle (days): How long, in days, between each batch of vested tokens is released. 

Cycle Release (percent): How many tokens will be released each cycle following the First Token Release batch. Please note this is expressed in percentage, not in number of tokens.

## Team Vesting 

PulseFinity not only secures projects through official audits but also provides projects with vesting protocols to ensure extra security. The Team Vesting System is a vesting protocol that asks project owners to lock their team tokens for a period of time. This in turn means there is no unlocked team tokens which could make a rug pull possible. This feature helps projects establish an increased level of trust with their investors, thereby potentially resulting in growth and longterm price appreciation. It also prevents scam projects from trying to withdraw and sell unlocked tokens at or soon after listing time.


---

# 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:

```
GET https://pulsefinity.gitbook.io/pulsefinity/launchpad/vested-sale.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.