Immunefi

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

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

Critical website and application bug reports will be rewarded with USD 10 000, only if the impact leads to a direct loss in funds involving an attack that does not require any user action at all. Additionally any impact that leads to “Retrieve sensitive data/files from a running server such as: database passwords,blockchain keys, etc (this does not include non-sensitive environment variables, open source code, or usernames” and to “Execute arbitrary system commands” would be rewarded USD 10 000 USD, which is 2x the standard amount for Web/App critical impact. All other impacts that would be classified as Critical, or an impact resulting in a theft of funds that does not fall under this definition, would be rewarded USD 5 000.

Repeatable Attack Limitations

In cases of repeatable attacks for smart contract bugs, only the first attack is considered if the smart contracts where the vulnerability exists can be upgraded, paused, or killed. If the attack impacts a smart contract directly holding funds that cannot be upgraded or paused, the amount of funds at risk will be calculated with the first attack being at 100% of the funds that could be stolen and then a reduction of 25% from the amount of the first attack for every 300 blocks the attack needs for subsequent attacks from the first attack, rounded down. For avoidance of doubt, if a second attack would happen at 600 blocks and then a third at 900 blocks, the funds at risk would be counted at 50% and 25% of the reward from the first attack, respectively.

Reward Calculation for High Level Reports High smart contract vulnerabilities will be capped at up to 100% of the funds affected. In the event of temporary freezing, the reward doubles for every additional 5 blocks that the funds could be temporarily frozen, rounded down to the nearest multiple of 5, up to the hard cap of USD 10 000 USD.

Restrictions on Security Researcher Eligibility

Security researchers who fall under any of the following are ineligible for a reward

• Countries that are restricted by OFAC and by UNSC resolutions.

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program.

• Any well-known issues related to Gnosis Safe: https://docs.gnosis-safe.io/learn/security/security-audits

Previous Audits Immunefi has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

• Here’s the internal audit of the Vaults System
• Here’s the Ourovoros audit of the Vaults System

Feasibility Limitations

Bug reports that require an attack that involve one or more other protocols (e.g. utilizing flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be downgrade by one severity level. However, they will be considered as in-scope and categorized according to the program rules as long as all of the following are true:

• Losses or other negative effects of the attack are inflicted upon Immunefi ecosystem participants (including Immunefi’s customers)

• The additional protocols used must have enough liquidity in various assets to allow the attack to succeed at the time of bug report submission. For example: if an attack requires an ETH flash loan, but the amount is larger than all the ETH available for loan across the ecosystem

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• All Smart Contract bug reports

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Other Terms and Information

Bug reports covering previously-discovered bugs are not eligible for the program. If a bug report covers a known issue, it may be rejected, and Immunefi will provide proof that the issue is already known.

Reward Payment Terms

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