BProtocol
B.Protocol’s BAMM is a novel DeFi primitive, providing better stability, and unlocking higher capital efficiency in the DeFi lending ecosystem. The protocol enables anyone to participate in the liquidation processes in DeFi, helping to maintain the supported platforms safe, while democratizing the process.
PoC required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% 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.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into account the funds at risk. Other considerations such as PR and branding concerns may also be considered by the team at its discretion.
Paid auditor(s) of this code is(are) not eligible for rewards in this table. Determinations of eligibility and final reward amount (for critical vulnerabilities) and all terms related to an award are at the sole and final discretion of the B.Protocol team.
Payouts are handled by the BProtocol team directly and are denominated in USD. Payouts are done in USDC or DAI for payouts up to USD 10 000 and BPRO/stablecoin mix (90%/10%) for all other critical payouts, capped by up to 50 000 BPRO.
Program Overview
B.Protocol runs a Backstopp AMM (BAMM) as a robust liquidation engine solution for DeFi lending platforms.
B.Protocol’s BAMM is a novel DeFi primitive, providing better stability, and unlocking higher capital efficiency in the DeFi lending ecosystem. The protocol enables anyone to participate in the liquidation processes in DeFi, helping to maintain the supported platforms safe, while democratizing the process.
B.Protocol pools users’ funds into Backstop pools. This liquidity is used for liquidations as they happen on integrated platforms. While the Backstop funds are sitting idle in the pools waiting for liquidation to occur, they gain either interest rates or liquidity mining rewards, or both, generating passive revenue for the Backstoppers - users who provide liquidity to the Backstop pools. Once a liquidation takes place, the Backstop AMM (BAMM) smart contract pulls the needed funds from the backstop to facilitate the liquidation and automatically puts the seized collateral for sale. Once sold, the return is deposited back to the backstop pool, and profits are accrued.
For more information about BProtocol, please visit https://www.bprotocol.org/.
The bug bounty program covers its smart contracts and is focused on the prevention of the negative impacts stated in the Impacts in Scope section.
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.