> 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/holder-protections.md).

# Holder Protections

Holder Protections is a **label** (a badge on Polypad token cards and token pages). It is not an NFT. It counts how many on-chain checks a token meets, grouped into tiers, and Explore can be filtered by minimum tier.

The label describes **on-chain settings only**. It is not a promise about price, liquidity, or what a creator will do off-chain. A token without protections is still a normal Polypad launch.

## What is checked

The Polypad site describes five on-chain checks. The checks documented in the repository and on the Polypad site include:

| Check               | What it means                                                                                                                                                                             |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Vesting label       | A creator vesting vault with a cliff of at least 30 days and a duration of at least 180 days. See [Creator vesting](https://polydash.gitbook.io/polydash-docs/polypad/creator-vesting.md) |
| Creator bond        | An ETH bond that backs a floor balance across registered wallets. See [Creator bond](https://polydash.gitbook.io/polydash-docs/polypad/creator-bond.md)                                   |
| Graduated liquidity | The launch has graduated into a Uniswap V4 pool with locked liquidity. See [Graduation](https://polydash.gitbook.io/polydash-docs/polypad/graduation.md)                                  |
| Staking committed   | An active staking pool created by the token creator. See [Staking pools](https://polydash.gitbook.io/polydash-docs/polypad/staking-pools.md)                                              |
| Security scan       | A clean automated security check. A scan is not a review                                                                                                                                  |

Holder Protections contracts are optional. The factory does not deploy them. A creator adds them after `createLaunch`.

## What the labels do not mean

* A vesting label does not mean a price will hold.
* A launch with no vault has no vesting label.
* A bond slashes only the posted ETH, and only when the registered wallets miss the floor.
* A scan is automated and can be incomplete or wrong.

## For creators

Add a vesting vault and a staking pool to move up a tier. Both are covered in this section.


---

# 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/holder-protections.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.
