Instadapp-logo

Instadapp

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.

Avalanche
BSC
ETH
Fantom
Optimism
Polygon
Defi
L1
L2
Wallet
Solidity
Maximum Bounty
$500,000
Live Since
20 September 2021
Last Updated
29 October 2024
  • PoC required

Rewards

Instadapp provides rewards in USDC, USDT, DAI on Ethereum, denominated in USD.

Rewards by Threat Level

Smart Contract
Critical
Max: $500,000Min: $25,000
Primacy of Rules
High
Max: $100,000Min: $5,000
Primacy of Rules
Websites and Applications
Critical
Max: $50,000Min: $5,000
Primacy of Rules
High
Max: $10,000Min: $5,000
Primacy of Rules

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

Avocado

Fluid

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.

Program Overview

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.

This bug bounty program covers the following protocols and services:

Instadapp PRO (DeFi Smart Accounts)

Instadapp PRO is a comprehensive platform for managing and utilizing DeFI, users can access the top lending protocols and maximize their gains by leveraging and refinancing between protocols. Instadapp Pro allows users to execute advanced swaps and other complex transactions.

Avocado Smart Wallet

Avocado is a next generation Account Abstraction wallet created by the Instadapp Team. Avocado abstracts networks, gas and addresses making it easier to interact with the growing and complex web3 world. Avocado features a unified USDC gas tank, mass payments, cross chain transaction, transaction previews, built in DEX and Bridging services and 2FA security.

Fluid

Fluid works as a multi-layered protocol with a unified liquidity layer that enables many protocols to be built on top:

  • Fluid Liquidity Layer: The base liquidity protocol for Fluid, all liquidity and protocols draw their liquidity from the liquidity layer.
  • Fluid Lending Protocol: foundational component designed to facilitate secure and highly efficient lending. You can think of it as the 'Deposit and Earn' of Fluid.
  • Fluid Vault Protocol: The first protocol built on top of the Liquidity Layer, the vault protocol enables users to supply assets and borrow against them in a single-asset/single-debt vault similar to MakerDAO.

For more information about Instadapp, please visit https://instadapp.io/.

This bug bounty program is focused on their smart contracts and dapp and is focused on preventing the following impacts:

  • Deletion of user data
  • Theft of governance funds
  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount

KYC not required

No KYC information is required for payout processing.

Proof of Concept

Proof of concept is always required for all severities.

Prohibited Activities

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

Severity
Min. - Max.
Critical
$5k -$500k
High
$5k -$100k
Total Assets in Scope
9