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.

Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network

Contract fails to deliver promised returns, but doesn't lose value

Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments

Direct loss of funds

Permanent freezing of funds (fix requires hardfork)

RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer

Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours

A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk

Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network

Modification of transaction fees outside of design parameters

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties

Permanent freezing of funds

Permanent freezing of NFTs

Unauthorized minting of NFTs

Predictable or manipulable RNG that results in abuse of the principal or NFT

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Protocol insolvency

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds

Temporary freezing of NFTs

Smart contract unable to operate due to lack of token funds

Block stuffing

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Network not being able to confirm new transactions (total network shutdown)

Unintended chain split (network partition)

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

__For Blockchain/DLT__

The set of attack vectors listed in this bullet list represents potential exploits that may result in one or more of the impacts defined in the table.

- Remote code execution on validator node
- Exposure of cryptographic key material
- Impersonation of validator’s authenticated actions, e.g. forging of signatures or votes
- Bugs that would allow the extraction, or the destruction, or the generation of surplus monetary rewards other than what is designated in the protocol
- Any bug that would lead to a perceivable advantage other than the validator’s voting power, e.g. election bias
- Confused deputy on equivocating or slashable behavior, e.g. the validator node is induced into voting twice involuntarily
- Attacks lead a percentage of nodes to crash, halting the chain
- Bugs leading to a percentage of nodes into an inconsistent state, without stopping the chain
- Non-generic attacks lead to a chain halt or make the chain unable to progress
- Safety and correctness flaws that would require the combination of extraordinary conditions to occur
- Extended degradation of performances by non-generic means 
- Non-generic attacks mean that there must be an omission or a defect in the code that would result in any significant computational advantage.

Beacon-kit codebase

Smart Contract Repo

Documentation

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 

__Reward Calculation for Critical Level Reports__

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.

__Repeatable Attack Limitations__

- 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. 

__Reward Calculation for High-Level Reports__

- 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.
 
__Reward Payment Terms__

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.

Berachain

Codebase

Documentation