However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Bifrost is a Liquid Staking app-chain tailored for all blockchains, utilizing decentralized cross-chain interoperability to empower users to earn staking rewards and DeFi yields with flexibility, liquidity, and high security across multiple chains.

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

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

Causing network processing nodes to process transactions from the mempool beyond set parameters

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

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

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

Execute arbitrary system commands

Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Redirecting users to malicious websites (open redirect)

Unintended chain split (network partition)

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Changing non-sensitive details of other users (including modifying browser local storage) w/o already-connected wallet interaction and w/ up to one click of user interaction, such as changing the first/last name of user, or enabling/disabling notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Direct fund losses caused by additional issuance of vTokens (e.g., vDOT, vKSM)

Direct fund losses caused by non-vToken additional issuance

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

Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)

Permanent freezing of funds (fix requires hardfork)

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). This is a simplified 4-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Payouts are handled by the __Bifrost Finance__ team directly and are denominated in USD. However, payouts are done in __BNC__.

__Reward Calculation for Critical Level Reports__

Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of: $100,000

For critical Blockchain/DLT bugs, 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.