BiFi

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

All bug reports require a PoC written in code to be eligible for a reward. Remember, you must attach a PoC written in code separately for quick analysis by our security engineers. Reports without a PoC will not be accepted, even if the issue is so obvious that a PoC is not needed.

The PoC must be reproducible, and if dependencies are required to run the PoC (e.g., Install hardhat and fork chain), the process of installing all dependencies must also be described, along with appropriate comments or explanations.

For an example of well-written PoC code, see the example below.

• https://github.com/immunefi-team/polygon-transferwithsig?tab=readme-ov-file

Responsible Publication

BiFi adheres to Publication Category 3 - Approval Required: Reporters are subject to restrictions on external disclosure for all publications they submit, see Responsible Publication Policy for more information.

Readability

Remember, reports must be readable for review. If the description is lacking or difficult for the BiFi project to understand, the BiFi team may require additional clarification or reject the report. Best report may be readable to a CS engineer who knows nothing about the basic vulnerability. For complex vulnerabilities, illustrations may be helpful.

Feasibility

Vulnerabilities that require manipulation outside the scope of BiFi, require administrator privileges to reproduce the attack, are non-reproducible bugs, or are not feasible for an attacker will not be rewarded.

Here are examples

• Manipulation of the BiFi external pricing oracle
• Vulnerabilities that require gaining administrator privileges or manipulation
• Spending more in gas fees to execute the attack than the amount gained from the attack
• These are the parts of the evaluation that are excluded.

The following vulnerabilities are not eligible for a reward:

• Using a single on-chain price oracle as a price feed source (e.g., Uniswap, Sushiswap)
• Decimal discrepancy that the BiFi team is aware of

Previous Audit

BiFi has had its code audited by Theori, which are web3 security specialists. Any unresolved findings from that audit will be excluded from the rewards. https://github.com/bifrost-platform/BIFI/tree/master/docs

Vulnerability Testing

Any activity on the Mainnet or Testnet to prove or validate the above vulnerabilities is strictly prohibited. PoC activities must be performed on a forked local chain. Testing performed on-chain for a bug bounty will be excluded from the reward.

Payouts are handled by the BiFi team directly and are denominated in USD. However, payouts are done in BFC, ETH, Stablecoin (USDT or USDC) with the choice of the ratio at the discretion of the team.