Zodiac
The expansion pack for DAOs, Zodiac is a collection of tools built according to an open standard. The Zodiac open standard enables DAOs to act more like constellations, connecting protocols, platforms, and chains, no longer confined to monolithic designs.
PoC required
KYC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 100 000 for Critical smart contract bug reports.
Gnosis requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is an invoice including:
- Full Name or Business Name
- Personal or Business Address
- Invoice number
- Invoiced amount and currency
Payouts are handled by the Gnosis team directly and are denominated in USD. However, payouts are done in ETH, DAI or GNO at the discretion of the team. Payouts may be done on either Mainnet or the Gnosis chain.
Program Overview
The expansion pack for DAOs, Zodiac is a collection of tools built according to an open standard.
The Zodiac open standard enables DAOs to act more like constellations, connecting protocols, platforms, and chains, no longer confined to monolithic designs.
For more information about Zodiac, please visit https://github.com/gnosis/zodiac.
For additional documentation on Zodiac, please refer to the links below:
- https://github.com/gnosisguild/zodiac-module-reality
- https://github.com/gnosisguild/zodiac-modifier-roles-v1
- https://github.com/gnosisguild/zodiac-module-bridge
- https://github.com/gnosisguild/zodiac-module-exit
- https://github.com/gnosisguild/zodiac-modifier-delay
- https://github.com/gnosisguild/zodiac-guard-scope
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Any governance voting result manipulation
- Theft of user or DAO funds
- Permanent freezing of user or DAO funds
- Causing DAO to execute arbitrary code
KYC required
The submission of KYC information is a requirement for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.