Berachain
Bounty Range
$2,000 - $250,000
external program
Berachain
Berachain is a high-performance EVM-Identical Layer 1 (L1) blockchain utilizing Proof-of-Liquidity (PoL) as a consensus mechanism and built on top of a modular EVM-focused consensus client framework named BeaconKit.
BeaconKit is a modular framework for building EVM-based consensus clients. The framework offers the most user-friendly way to build and operate an EVM blockchain while ensuring a functionally identical execution environment to the Ethereum Mainnet.
For more information about Berachain, please visit the docs or code repositories.
Berachain provides rewards in BERA on Berachain, denominated in USD.
Critical
High
Medium
Low
Critical
High
Medium
Low
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $250,000. However, a minimum reward of USD $50,000 is to be rewarded to incentivize security researchers against withholding a bug report.
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $250,000. Calculating the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $50,000 is to be rewarded to incentivize security researchers against withholding a critical bug report.
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.
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. The project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within $10,000 to $50,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for more significant damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures more substantial incentives for bug disclosure of this nature.
Payouts are handled by the Berachain team directly and are denominated in USD. However, payments are made in BERA on Berachain.
The net amount rewarded is calculated based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Berachain will be requesting KYC information 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 outlined in this program and cannot be:
Berachain adheres to category 3 - Approval Required. This Policy determines what information researchers can make public from their submitted bug reports.
Berachain adheres to the Primacy of Rules, meaning the whole bug bounty program is run strictly under the terms and conditions stated on this page.
A PoC demonstrating the bug's impact is required for this program and must comply with the Immunefi PoC Guidelines and Rules.
Proof of concept is always required for all severities.
Bug reports covering previously discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Known issues can be found in:
Current known issues related to the Berachain Airdrops Contract are presented in the following audit reports:
Previous audits can be found at: https://github.com/berachain/security-audits
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.
Immunefi has developed feasibility limitation standards which by default state what security researchers, as well as projects, can or cannot cite when reviewing a bug report, including:
By adhering to Immunefi's best practice recommendations, Berachain has satisfied the requirements for the Immunefi Standard Badge.