Avocado (excluding the helper folder within avo-contracts)

Fluid Liquidity Layer, Fluid Lending protocol, Fluid Vault protocol. Fluid Contracts (excluding periphery folder)

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

All folders and files labeled with the words “test”, “mock/mocks”, or “dummy” are out-of-scope of the bug bounty program.

The Instadapp platform offers a comprehensive suite of tools for both users and developers to harness the full potential of DeFi. With products ranging from refinancing and flashloan strategies to lending platforms and smart wallet protocols, Instadapp aims to optimize DeFi interactions.

Any governance voting result manipulation

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield (Connectors are out of scope from this)

Permanent freezing of funds

Protocol Insolvency

Ability to execute system commands

Extract Sensitive data/files from the server such as /etc/password

Bypassing Authentication

Signing transactions for other users

Redirection of user deposits and withdrawals

Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)

Wallet interaction modification resulting in financial loss

Direct theft of user funds

Tampering with transactions submitted to the user’s wallet

Submitting malicious transactions to an already-connected wallet

Theft of unclaimed yield

Miner-extractable value (MEV)

Permanent freezing of unclaimed yield

Temporary freezing of funds (more than 10 Days)

Spoofing content on the target application (Persistent)

Users Confidential information disclosure such as Email

Privilege escalation to access unauthorized functionalities

Third-Party API keys leakage that demonstrates loss of funds or modification on the website

Redirecting users to malicious websites (Open Redirect)

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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

__Reward Calculation for Critical Level Reports__

For critical smart contract vulnerabilities, the reward is 10% of the directly affected funds, up to a maximum of USD 500,000. The calculation considers the funds at risk based on the bug report submission date and time. There is a minimum guaranteed reward of USD 25,000 to encourage reporting even for smaller valued critical bugs.


__Reward Calculation for High Level Reports__

For high smart contract impacts, the reward is capped at $100,000 and is based on 50% of the value of the affected funds. The calculation considers the funds at risk based on the bug report submission date and time. There is a minimum guaranteed reward of USD 5,000 to encourage reporting even for smaller valued critical bugs.

__Secondary/Market Attack on Fluid__

Fluid as a lending protocol utilizes different aspects of the blockchain which may indirectly affect the protocol. The following outline conditions for particular secondary attacks that are not directly on the Fluid contracts, but that have secondary or associated effects to the Fluid contracts may be considered for a reward:

- The attack must directly impact Fluid i.e an attack which affects the broader market such as price manipulation but is not targeting Fluid would not qualify.

Examples of secondary attacks would be:

- Manipulation of a DEX or on Chain price oracle from a secondary source, which results in the immediate and total loss of funds of the Fluid protocol, where the attack is specifically targeting Fluid protocol.
- Flash Loan based attack that would cause immediate and irreversible financial loss to Fluid protocol; where the attack is specifically targeting the Fluid protocol, this would exclude attacks which manipulate the price of a single token used on Fluid.

Prior published audits are here for review, any noted vulnerability or bugs in previously completed audits are not eligible for a reward.

Defi Smart Accounts (DSA)/Instadapp PRO
- [Peckshield - Mar 16, 2021](https://github.com/Instadapp/dsa-contracts/blob/master/audits/v2_PeckShield_Mar_2021.pdf)
- [Peckshield - Mar 18, 2020](https://github.com/Instadapp/dsa-contracts/blob/master/audits/v1_PeckShield_Mar_2020.pdf)
- [Samczun Audit - Mar 2020](https://github.com/Instadapp/dsa-contracts/blob/master/audits/v1_samczsun_Mar_2020.md)

Avocado
- [Statemind - Sept 28, 2023](https://github.com/Instadapp/avocado-audits/blob/main/Statemind-Audit-Report-Avocado-v3.pdf)
- [Peckshield - June 12, 2023](https://github.com/Instadapp/avocado-audits/blob/main/PeckShield-Audit-Report-Avocado-v3.pdf)

Fluid
- [Statemind - Dec 29th, 2023](https://github.com/statemindio/public-audits/blob/main/Instadapp/2023-12-29_Instadapp_Fluid.pdf)

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:

- Smart Contract - Critical
- Smart Contract - High

When calculating the USD value of total value locked (TVL) to determine funds at risk, outstanding borrows are excluded.

To be eligible for a reward, the vulnerability must exist in the deployed smart contract.

Bugs resulting in temporary freezing of funds are not eligible for a reward. 

Payouts are handled by the Instadapp team directly and are denominated in USD. However, payouts are done in stablecoins like, USDC, USDT and DAI at the discretion of the team.

Instadapp

Resources & Documentation