
Hedera
Bounty Range
$3,000 - $30,000
external program
Hedera is a fully open source, proof-of-stake, public network and governing body for building and deploying decentralized applications. It offers developers three primary services: Solidity-based smart contracts, consensus, and token services. Hedera is unique in that it is incredibly fast, energy-efficient (carbon negative), and secure — these advantages can be attributed to its underlying hashgraph consensus algorithm.
For more information about Hedera, please visit https://hedera.com/
Hedera provides rewards in USDC on Ethereum, denominated in USD.
Critical (Blockchain/DLT)
High
Medium
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $30,000.
Minimum reward to discourage security researchers from withholding a bug report: $10,000
The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward [$30,000]. However, a minimum reward of USD [$10,000] is to be rewarded in order to incentivize security researchers against withholding on a bug report.
Hedera will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
Proof of concept is always required for all severities.
Category 3: Approval Required
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.