21 October 2021
Live since
No
KYC required
$100,000
Maximum bounty
23 May 2024
Last updated

Program Overview

BiFi is the Multichain DeFi Project built on BIFROST, the Universal Multichain Middleware. BiFi aims to create a decentralized financial infrastructure that connects all the capital markets currently isolated on each blockchain, and creates new products and services that interoperate across multiple blockchains.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Thefts and freezing of governance funds
  • Thefts and freezing of permission among contracts
  • Manipulations of the contract functionality (DoS, Malicious Re-entrancy, etc.)

Rewards by Threat Level

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.

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.

Smart Contract

Critical
Level
USD $100,000
Payout
PoC Required
High
Level
USD $20,000
Payout
PoC Required
Medium
Level
USD $2,000
Payout
PoC Required
Low
Level
USD $1,000
Payout
PoC Required

Assets in scope

All smart contracts of Bifi can be found at https://github.com/bifrost-platform/BIFI. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts in scope

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

Smart Contract

  • Any governance voting result manipulation
    Critical
    Impact
  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
    Critical
    Impact
  • Permanent freezing of funds
    Critical
    Impact
  • Protocol Insolvency
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Permanent freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds
    High
    Impact
  • Block stuffing for profit
    Medium
    Impact
  • Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
    Medium
    Impact
  • Theft of gas
    Medium
    Impact
  • Unbounded gas consumption
    Medium
    Impact
  • Contract fails to deliver promised returns, but doesn't lose value
    Low
    Impact

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • Attacks that the reporter has already exploited themselves, leading to damage
  • Attacks requiring access to leaked keys/credentials
  • Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
  • Any testing with pricing oracles or third party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • Any denial of service attacks
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty