All smart contracts of SingularityDAO can be found at [https://github.com/Singularity-DAO/dynaset-contracts](https://github.com/Singularity-DAO/dynaset-contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by SingularityDAO that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. Bugs found in third party assets are not accepted. 

SingularityDAO is a decentralised Portfolio Management Protocol designed to enable anybody to safely and easily manage crypto assets, supported by superior risk management and analytics tools; smart money, on-chain. A non-custodial protocol to foster a new ecosystem of Digital Asset Managers to offer automated trading strategies leveraging AI-enchanted data analytics services.

Any governance voting result manipulation (excluding manipulating third party websites)

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

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds for at least 120 minutes (excluding vaults that requires and features users to lock/freeze their funds)

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

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

Theft of gas

Unbounded gas consumption

Smart contract fails to deliver promised returns, but doesn’t lose value

Rewards are distributed according to the impact of the vulnerability based on the  [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Known issues highlighted in the following audit reports are considered out of scope: 
- [https://hacken.io/wp-content/uploads/2022/04/SDAO-TokenConversion_16032022SCAudit_Report_3.pdf](https://hacken.io/wp-content/uploads/2022/04/SDAO-TokenConversion_16032022SCAudit_Report_3.pdf)
- [https://hacken.io/wp-content/uploads/2022/04/SDAO-UpgradableTokens_10032022SCAudit_Report.pdf](https://hacken.io/wp-content/uploads/2022/04/SDAO-UpgradableTokens_10032022SCAudit_Report.pdf)
- [https://hacken.io/wp-content/uploads/2022/04/SDAO-Dynaset_15122021SCAudit_Report_2.pdf](https://hacken.io/wp-content/uploads/2022/04/SDAO-Dynaset_15122021SCAudit_Report_2.pdf)
- [https://hacken.io/wp-content/uploads/2022/04/SDAO-Airdrop_14012022SCAudit_Report_3.pdf](https://hacken.io/wp-content/uploads/2022/04/SDAO-Airdrop_14012022SCAudit_Report_3.pdf)
- [https://hacken.io/wp-content/uploads/2022/04/SDAO_30082022_SCAudit_Report-2.pdf](https://hacken.io/wp-content/uploads/2022/04/SDAO_30082022_SCAudit_Report-2.pdf)
- [https://hacken.io/wp-content/uploads/2022/04/SDAO_Dydx_30082022_SCAudit_Report-2.pdf ](https://hacken.io/wp-content/uploads/2022/04/SDAO_Dydx_30082022_SCAudit_Report-2.pdf)

Payouts are handled by the __SingularityDAO__ team directly and are denominated in USD. However, payouts are done in __USDC__ or __SDAO__, at the discretion of the project.


SingularityDAO

Resources & Documentation