Instadapp

Back to Explore 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 Optimism Polygon Defi L1 L2 Wallet Solidity Maximum Bounty $500,000 Live Since 20 September 2021 Last Updated 07 November 2026 PoC Required Submit a Bug Information Scope Resources Rewards Instadapp provides rewards in USDC, USDT, DAI on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $500,000 Min: $10,000 Primacy of Rules High Max: $100,000 Min: $5,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $500,000 Minimum reward to discourage security researchers from withholding a bug report: $10,000 Websites and Applications Critical Max: $50,000 Min: $5,000 Primacy of Rules High Max: $10,000 Min: $5,000 Primacy of Rules Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3 . This is a simplified 4-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. Where the rules on this program page differ from the Severity Classification System V2.3, the rules on this page take precedence. 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 10,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 high severity bugs. Severity and Funds at Risk The Severity Classification System V2.3 lists "Direct theft of any user funds" and "Permanent freezing of funds" as Critical without regard to the amount affected. On this program, that is overridden where the funds at risk are small and there is no direct path for the funds at risk to increase. Admin actions do not count as such a path. Examples are funds at risk that are limited by hard limits, or a deprecated contract that still holds funds but that no new users can enter. In these cases the funds actually at risk in the affected contracts at the time of submission are part of the severity rating, and the finding may be classified at a lower severity than its impact category alone suggests. 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. Repeatable Attacks on Pausable Contracts Fluid contracts can be paused by the protocol guardians. Where the vulnerable contract can be paused or upgraded, only the initial attack is considered for the reward, as Fluid can mitigate further exploitation by pausing or upgrading the affected component; repeated or looped extraction after the first attack is not compounded into severity or reward. For contracts that cannot be paused or upgraded, the Repeatable Attack Limitations configured for this program apply (25% reduction per additional attack, 1-hour interval). Audits 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 Peckshield - Mar 18, 2020 Samczun Audit - Mar 2020 Avocado Statemind - Sept 28, 2023 Peckshield - June 12, 2023 Fluid Statemind - Dec 29th, 2023 Proof of Concept (PoC) Requirements A Proof of Concept is required for all severity levels (Critical, High, Medium and Low), for every asset type in scope. 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 for under 10 days are not eligible for a reward. Temporary freezing of funds for more than 10 days is assessed under the in-scope High impact. Payouts are handled by the Instadapp team directly. Payouts are made in USDC, USDT or DAI on Ethereum, denominated in USD. Scope Clarifications Issues affecting the first or last user of a pool or vault that arise from dust amounts, in any protocol other than DexV2, are classified at most as Low, since the standard production setup includes seeding a dust position that serves as the first and last user. A vulnerability present in both the EVM and Solana codebases is treated as a single finding and rewarded once, not as two separate reports. Deployed contract addresses are listed in deployments.md in the public repository; funds at risk is assessed against the deployed contracts referenced there. Deprecated Contracts Contracts marked as deprecated in the public deployments file ( https://github.com/Instadapp/fluid-contracts-public/blob/main/deployments/deployments.md ) remain in scope for as long as they hold funds. For findings on deprecated contracts, the minimum reward is one tenth of the standard minimum: USD 1,000 for Critical and USD 500 for High. View impacts in scope 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 Thefts and freezing of unclaimed yield Audits Auditor Link Completed at Fluid Technical Docs — all audits │ https://docs.fluid.io/audits-and-security.html │ 8 September 2026 Auditor Fluid Technical Docs — all audits Link https://docs.fluid.io/audits-and-security.html Completed at 8 September 2026 KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 6