BiFi
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.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is % of the funds directly affected up to a maximum of:
$100,000Rewards 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.
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.
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.)
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
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.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.
250.00