BendDAO
Bend DAO is the first decentralized peer-to-pool based NFT liquidity protocol. Borrowers can borrow ETH instantly through the lending pool using NFTs as collateral. Depositors provide ETH liquidity to the lending pool to earn interest.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of numerous user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds of numerous user
Insolvency
Theft of unclaimed yield of numerous users
Permanent freezing of unclaimed yield of numerous users
Direct theft of individual user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds of individual user
Smart contract unable to operate and call ( e.g. destruct of code, lack of funds)
Theft of unclaimed yield of individual user
Permanent freezing of unclaimed yield of individual user
Manipulation of interest rates (supply or borrow) with mechanisms not intended or limited by design
Smart contract unable to operate and call ( e.g. destruct of code, lack of funds)
Out of scope
-
Best practice critiques
-
Any DoS or DDOS on the smart contracts
-
Third-party bugs that have no impact on the BendDAO protocol
-
Dev branches that are not deployed in public packages or contracts
-
Third party contracts that are not under the direct control of BendDAO
-
Issues already listed in the audits for the contracts above
-
Bugs in third party contracts or applications that use BendDAO contracts
-
Rounding errors
-
Extreme market turmoil vulnerability
-
Gas optimization recommendations
-
Any MEV Attacks (e.g. Sandwich, Front-Running)
-
Public disclosure of bugs without the consent of the protocol team.
-
Conflict of Interest: any employee or contractor who currently works, or previously worked, with BendDAO cannot participate in the Bug Bounty without prior approval. Examples include Huma contributors, security researchers who worked on Huma Finance code reviews, etc.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers