Security

Polypad contracts are unaudited. Source code is public and verified on Sourcify where applicable. This page is our public security commitment: how to report a problem, what protects researchers who rescue funds during an exploit, what the automated scanners say, and the issues we already know about. Full policy: SECURITY.md. Live contract addresses: polypad.family/contracts.

Report a vulnerability

Email jon@dasheco.xyz with the subject "Security report", or open a private advisory from the Security tab of https://github.com/polydash-labs/Polydash. Include the contract address, the impact, and a proof of concept. Please do not open public issues for security problems, and allow reasonable time for a fix before disclosing. We aim to acknowledge reports within 72 hours.

No monetary rewards. Polydash does not offer money for vulnerability reports — there is no bug bounty budget. Researchers who report valid issues in good faith receive public credit in the fix notes if they wish to be named. Good-faith research that follows this policy will not be pursued legally.

SEAL Safe Harbor

Polypad is adopting the SEAL Safe Harbor Agreement for Whitehats (v3). During an active exploit, whitehats may rescue funds under the agreement and keep a rescue reward deducted from the rescued funds: 10% of rescued funds, capped at $2,500 per whitehat, with no aggregate cap. No payment comes from the project's funds. Pseudonymous whitehats are accepted, subject to sanctions screening. Rescued funds must reach the asset recovery address within 72 hours.

Status: terms published; on-chain registration in progress. The agreement address and registration transaction will be listed here once registered. The rescue reward is not a bug bounty — it only applies when a whitehat rescues funds during an active exploit.

Automated scans

Known issues

Staking factory v1 — fee recipient can freeze exits. In the v1 pool, a non-zero unstake fee is sent to the factory fee recipient before the staker's principal is returned. If that transfer reverts, withdraw, exit and emergencyWithdraw all revert. V1 is legacy with a single third-party pool; the owner keeps the fee recipient set to an address the stake token will transfer to. V2 pools are not affected.

Staking factory v2 (legacy) — fee-on-transfer reward tokens can freeze claims. In the legacy v2 pool, a fee-on-transfer reward token makes a claim near the remaining balance revert, freezing rewards. No live impact: all live pools on the legacy v2 factory use POLYDASH as both stake and reward token. Fixed in the current factory (0x4C87aff7009DE1c58E052FEe202349a10b28Be9c), which new pools use. Full detail in SECURITY.md.

Active-exploit emergency

If an exploit is happening right now, contact SEAL 911: t.me/seal_911_bot (free 24/7 emergency triage).

Contracts are unaudited. Automated scans are not audits. Not financial advice.