All code of ParagonsDAO can be found at [https://github.com/ParagonsDAO/pdt-staking.](https://github.com/ParagonsDAO/pdt-staking) Documentation for the assets provided in the table can be found at [https://docs.paragonsdao.com/docs/staking/staking-guide.](https://docs.paragonsdao.com/docs/staking/staking-guide)  

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about [Reported Subdomain Takeovers.](https://immunefisupport.zendesk.com/hc/en-us/articles/14352199704593-Reported-Subdomain-Takeovers)

ParagonsDAO is a community of gamers and investors bridging gaps across traditional gaming, web3 gaming, and decentralized finance (DeFi). Through ParagonsDAO Token ($PDT), you can share in the success of ParagonsDAO (and our game/business partners) through ownership and direction of our Treasury, revenue streams, community, proprietary DeFi solutions and much more!

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties

Permanent freezing of funds

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as: /etc/shadow, database passwords, blockchain keys, (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions

Injection of malicious HTML or XSS through NFT metadata

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds

Injecting/modifying the static content on the target application without Javascript (Persistent) such as: HTML injection without Javascript, Replacing existing text with arbitrary text, Arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Email or password of the victim, etc.

Improperly disclosing confidential user information such as: Email address, Phone number, Physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Changing the name of user, Enabling/disabling notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, Loading external site data

Redirecting users to malicious websites (Open Redirect)

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

__Previous Audits__

ParagonsDAO has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://pub-219b30570f3a4406a348a79b73b8c1b5.r2.dev/staking-CertiK.pdf ](https://pub-219b30570f3a4406a348a79b73b8c1b5.r2.dev/staking-CertiK.pdf)
- [https://pub-219b30570f3a4406a348a79b73b8c1b5.r2.dev/staking-PeckShield.pdf ](https://pub-219b30570f3a4406a348a79b73b8c1b5.r2.dev/staking-PeckShield.pdf)

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract, Critical Severity Level 
- Smart Contract, High Severity Level 
- Smart Contract, Medium Severity Level 
- Websites & Application, Critical Severity Level 
- Websites & Application, High Severity Level 
- Websites & Application, Medium Severity Level 

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the ParagonsDAO team directly and are denominated in USD. However, payments are done in USDC.

ParagonsDAO

Resources & Documentation