All code of Drips can be found at [https://github.com/orgs/drips-network/repositories.](https://github.com/orgs/drips-network/repositories) Documentation for the assets provided in the table can be found at [https://docs.drips.network/. ](https://docs.drips.network/)

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)


Drips is an Ethereum protocol and web app that makes it easy for organizations and individuals to provide direct financial support to developers of free and open source software (FOSS).

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

Permanent freezing of NFTs

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Protocol insolvency

Temporary freezing of funds

Temporary freezing of NFTs

Smart contract unable to operate due to lack of token funds

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

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

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 100 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 50 000 is to be rewarded in order to incentivize security researchers against withholding a bug report. 

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 50 000.

__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.

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- [https://hackmd.io/6_EgTHw6TVGlfxls0iKMAQ?view](https://hackmd.io/6_EgTHw6TVGlfxls0iKMAQ?view)

__Previous Audits__

Drips has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://docs.drips.network/assets/files/Spearbit_Drips_Network_Security_Review-d5cda225c36d4c2f1185e154431812b5.pdf](https://docs.drips.network/assets/files/Spearbit_Drips_Network_Security_Review-d5cda225c36d4c2f1185e154431812b5.pdf)
- [https://docs.drips.network/assets/files/Drips_Audit_Report-c2efbc01f0ce28c8847226339d63c3a7.pdf](https://docs.drips.network/assets/files/Drips_Audit_Report-c2efbc01f0ce28c8847226339d63c3a7.pdf)
- [https://code4rena.com/reports/2023-01-drips](https://code4rena.com/reports/2023-01-drips)
- [https://docs.drips.network/assets/files/Certora_Radicle_Drips_Report-a557b047cd7806033d47cfcba1ce334e.pdf](https://docs.drips.network/assets/files/Certora_Radicle_Drips_Report-a557b047cd7806033d47cfcba1ce334e.pdf)

__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 ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards)which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

__Proof of Concept (PoC) Requirements__

A PoC is required for the all Smart contract and Web/App severity levels

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.

__Other Terms and Information__

Exceptions to the PoC requirement for smart contract bugs may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

For smart contract-related vulnerabilities, in order to be eligible for a reward, the vulnerability must exist both in the deployed smart contract on Ethereum Mainnet and the GitHub file in the Assets in Scope table.

__Reward Payment Terms__

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


Drips

Resources & Documentation