Holdefi

Holdefi is a decentralized open-source non-custodial money market protocol where users can participate as depositors or borrowers. Depositors provide liquidity to the market to earn a passive income, and everyone can borrow from this liquidity and repay it after a while. The Borrower must add collateral before borrowing any tokens. The value of the collateral should be greater than the value of the assets they want to borrow. This collateral is, in fact, a guarantee that they will repay the borrowed assets.

For more information about Holdefi, please visit their website at https://holdefi.com/.

The bug bounty program is focused on the prevention of negative impacts to its smart contracts. Please see the Impacts in Scope section below for more information on the specific impacts it wishes to prevent.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.

Payouts are handled by the Holdefi team directly and are denominated in USD. All payouts are done in BUSD or USDC, at the discretion of the Holdefi team. Bug bounty hunters must indicate whether the address they are providing is an Ethereum address or one on the Binance Smart Chain (BSC).

For additional information, please reference their GitHub link for their smart contracts here -

https://github.com/holdefi/Holdefi/tree/master/contracts.

However, only the smart contracts listed as in-scope in this table are considered for the bug bounty program.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed interest
• Freezing of unclaimed interest
• Temporary freezing of funds for 1 hour
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns

We are especially interested in receiving and rewarding vulnerabilities of the following types, as long as they result in impacts stated in the Impacts in Scope section of this bug bounty program:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty