Submit a Bug
14 July 2021
Live since
KYC required
Maximum bounty
31 May 2023
Last updated

Program Overview

B.Protocol is DeFi’s Backstop Liquidity protocol, handling liquidations in scale for DeFi lending platforms. By creating a transparent, committed, smart contract-based liquidation system, B.Protocol enables better capital efficiency for DeFi users, while creating another layer of stability for the lending platforms themselves.

B.Protocol is integrated with existing lending platforms (MakerDAO, Compound, and soon others) via a dedicated smart contract interface where users give priority to the Backstop liquidators in the liquidation process. As this eliminates the gas wars between liquidators and gives them more certainty in the liquidations process, the Backstop liquidators share their proceeds with the Users in return, creating a win-win situation for all parties involved - User, Liquidators, and Platforms alike. The protocol API to end-users is identical to the lending platform API, and the only difference is that the users are interacting with different addresses. 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.

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.

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.

Smart Contract

Up to USD $100,000
USD $10,000
USD $5,000
USD $1,000

Assets in scope

The contracts in this table can be found on the following links:




However, only the smart contracts within the assets in scope table itself are considered as in-scope for 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

  • Critical Smart Contract Impact
  • High Smart Contract Impact
  • Medium Smart Contract Impact
  • Low Smart Contract 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