Bug Bounty

Program overview

In order to provide best in class security for our users, we have created a bounty program for individuals who identify issues in our protocol.
If you have found bug please submit here and alert one of our Discord moderators in a private message. Please do not disclose the bug publicly for security purposes.

Rewards by threat level

Rewards are distributed according to the exploitability level of the vulnerability and its impact based on the Immunefi Vulnerability Severity Classification System.
All bounties are capped at a maximum of 10% of the funds potentially affected.
Critical - Empty or freeze the contract’s holdings
Up to $500,000
High - Token holders temporarily unable to transfer holdings
Up to $5,000
Medium - Denial of Service (e.g. unbounded gas, block stuffing)
Up to $500
Low - Contract fails to deliver promised returns (e.g. high-level economic errors)
Up to $250
None - N/A
Payouts are handled by Badger directly. Payouts are denominated in USD and are paid out in the reporter’s choice of:

Assets in Scope

Prioritized vulnerabilites

We are especially interested in receiving and rewarding vulnerabilities of the following types:
    Logic errors
      including user authentication errors
    Solidity/EVM details not considered
      including integer over-/under-flow
      including unhandled exceptions
    Trusting trust/dependency vulnerabilities
      including composability vulnerabilities
    Oracle failure/manipulation
    Economic/financial attacks
      including flash loan attacks
    Congestion and scalability
      including running out of gas

Out of Scope

The following vulnerabilities are not eligible for bounties under this program:
    Theoretical vulnerabilities without any proof or demonstration
    Incorrect data supplied by third party oracles
    Basic economic governance attacks (e.g. 51% attack)
    Lack of liquidity
    Best practice critiques


The following actions and behaviors are prohibited. Doing so will prevent collection of a bounty and may result in prosecution:
    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 employees and/or customers
    Testing any denial of service attacks
    Automated testing of services that generates significant amounts of spam transactions
    Disassembly or reverse engineering of binaries for which source code is not published, not including smart contract bytecode
    Public disclosure of an unpatched vulnerability
Last modified 8mo ago
Copy link