> 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/report-a-vulnerability.md).

# Report a vulnerability

Please **do not** open public issues for security problems. Report privately.

## How to report

* Open a private advisory on GitHub: the repository's Security tab, then **Report a vulnerability**.
* Or message the team on Telegram: [@Johhnnylaw31](https://t.me/Johhnnylaw31).

Include the affected contract and address, the impact, and a proof of concept. A failing Foundry test is ideal. Test only on a local fork. Never test against live contracts or real user funds.

Polydash aims to acknowledge reports within 72 hours and to keep you updated until resolution. Please allow reasonable time for a fix before public disclosure.

## Bug bounty

Polydash runs a small self-hosted bug bounty for its staking contracts.

| Severity | Example impact                                                         | Reward      |
| -------- | ---------------------------------------------------------------------- | ----------- |
| Critical | Theft or permanent freezing of staked funds or unclaimed rewards       | Up to $100  |
| High     | Temporary freezing of funds, or rewards paid incorrectly               | Up to $50   |
| Medium   | Griefing or denial of service with no direct loss of funds             | Up to $25   |
| Low      | A contract fails to deliver its stated behavior, with no funds at risk | Recognition |

The total bounty budget is **$100**. Rewards are paid in USDC or $POLYDASH at the team's choice, to the earliest valid report of each issue. The Polydash team decides severity and amounts.

### In scope

* Staking factory V2 [`0x904b8F5d95B593b5F4a6Dbb116b58e1d5CBe93f0`](https://robinhoodchain.blockscout.com/address/0x904b8F5d95B593b5F4a6Dbb116b58e1d5CBe93f0) and its pools.
* Staking factory V1 [`0x0aAEa47d2e7303EC5a809062eafa59e7F011D857`](https://robinhoodchain.blockscout.com/address/0x0aAEa47d2e7303EC5a809062eafa59e7F011D857) (legacy).

### Out of scope

* The $POLYDASH token contract, a standard Clanker deployment.
* Third-party contracts and protocols such as Uniswap, Clanker, bridges, and oracles.
* Websites, front ends, Telegram bots, and other off-chain infrastructure.
* Issues that need a compromised owner key, social engineering, or phishing.
* Known issues listed in the docs, and gas optimizations.

## Known issue: V1 staking exit freeze

Reported by r00k of Hey Research Lab. In V1 staking pools, a non-zero unstake fee is sent to the factory's fee recipient before principal is returned. If that transfer reverts, `withdraw`, `exit`, and `emergencyWithdraw` all revert. This can happen when a stake token blocks the recipient, such as a blocklist token. V1 is legacy and has one third-party pool. Mitigation: the factory owner keeps `feeRecipient` set to an address the stake token accepts, and can rotate it to unfreeze exits. V2 does not push a fee during exit and is not affected.

## Scope note

All contracts are **Not audited.** An outside review is planned.

## Rules

* Test only on a local fork. Never test against live contracts or real user funds.
* Do not disclose an issue publicly before it is fixed.
* A clear proof of concept is required for any reward.
* Good-faith research that follows this policy will not be pursued legally.


---

# 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/report-a-vulnerability.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.
