> 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/security-and-risk.md).

# Security overview

What has and has not been checked, how to report a problem, and the risks of using Polydash products.

{% hint style="danger" %}
**Not audited.** The Polydash and Polypad contracts have not had a formal outside review. An outside review is planned. Using these contracts can result in loss of funds.
{% endhint %}

## What has been done

| Measure               | What it is                                                                                                                                                                 | What it is not                             |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| Open source           | Contracts, tests, and agents are public on GitHub                                                                                                                          | Proof that the code is correct             |
| Sourcify verification | Published source matches deployed bytecode for the contracts marked in the [Contract registry](https://polydash.gitbook.io/polydash-docs/smart-contracts.md)               | A review of behavior                       |
| Foundry tests         | Unit, fuzz, invariant, and fork tests                                                                                                                                      | Proof that no bugs exist                   |
| CI and Slither        | An advisory static-analysis job on every change                                                                                                                            | A review. Findings are triaged by the team |
| Bug bounty            | A small self-hosted program for the staking contracts. See [Report a vulnerability](https://polydash.gitbook.io/polydash-docs/security-and-risk/report-a-vulnerability.md) | Full coverage                              |

## Design choices that reduce trust

* **Non-custodial.** You sign every action. Polypad never holds keys.
* **No owner on launched tokens.** No mint, pause, blacklist, or transfer tax.
* **Locked liquidity.** The Polypad hook has no code path to remove graduated liquidity.
* **Fixed fees.** The 0.2% platform fee is a code constant. Creator fees are fixed at launch.
* **Time locks.** Fee wallet changes, creator payout changes, treasury actions, and buyback target changes wait behind public time locks.
* **Not upgradeable.** Staking pools and factories are immutable. Launch contracts are minimal clones of a fixed implementation that the factory holds as an immutable.
* **Defensive token handling.** Balances are measured by balance deltas, external calls are non-reentrant, and ERC-20 transfers use `SafeERC20`.

See [Owner capabilities](https://polydash.gitbook.io/polydash-docs/polypad/owner-capabilities.md) for exactly what the factory owner can and cannot do.

## Known limits

* Staking V1 is legacy. A fee recipient that rejects a stake token can freeze exits in V1. V2 is not affected. Do not use V1 for new pools.
* The V1 reward accumulator can round to zero with a 6-decimal reward token and a very large 18-decimal stake supply.
* Staking pools do not support rebasing tokens or tokens with transfer hooks or blocklists.
* Funds depend on price feeds. A missing or stale feed makes net value reads revert.
* The floor vault and buyback contracts bound execution cost, not market outcome.
* Labels such as Agent-launched, Build, and Holder Protections describe settings or links. They do not review a token.

## What is not covered

Third-party contracts and services carry their own risks, including Uniswap, Clanker, bridges, oracles, wallets, RPC providers, and explorers. Websites and front ends are outside the contract scope.

## Related

* [Risk disclosure](https://polydash.gitbook.io/polydash-docs/security-and-risk/risk-disclosure.md)
* [Report a vulnerability](https://polydash.gitbook.io/polydash-docs/security-and-risk/report-a-vulnerability.md)
* [Verification and source](https://polydash.gitbook.io/polydash-docs/smart-contracts/verification-and-source.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://polydash.gitbook.io/polydash-docs/security-and-risk.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.
