Badger DAO
Badger Finance is a community DAO, focused on bringing Bitcoin to DeFi. The DAO's debut products are Sett, a yield aggregator, and Digg, a BTC-pegged elastic supply currency. Its components include:
Triaged by Immunefi
PoC required
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.
Rewards for critical payouts are capped at 10% of the funds at risk.
POC required for all medium, high, and critical bug reports
Payouts up to USD 500 000 are handled by the BadgerDAO team directly and are denominated in USD. Payouts are denominated in USD and are paid out in the reporter's choice of BADGER, ETH, BTC, or a stablecoin (USDC, DAI, USDT).
Program Overview
Badger Finance is a community DAO, focused on bringing Bitcoin to DeFi. The DAO's debut products are Sett, a yield aggregator, and Digg, a BTC-pegged elastic supply currency. Its components include:
- Badger DAO - The governance of Badger Finance is managed via an Aragon DAO with a liquid governance token.
- Sett - The debut yield aggregator product of the DAO, focused on innovating on the best bitcoin-related yield strategies.
- Digg - A BTC-pegged elastic supply currency, based on the Ampleforth protocol.
- Token Distribution - The Badger governance token ($BADGER) and the Digg token ($DIGG) will be initially distributed via airdrops for users who have demonstrated an active interest in Bitcoin DeFi and community governance, early contributors to the DAO, and as staking rewards for participation in Sett.
- Assistants - Traditional backend services to provide necessary updates to the system. These include oracles, keepers, and system monitors
The bug bounty program is focused around its smart contracts and is mostly concerned with the loss of user funds.
KYC not required
No KYC information is required for payout processing.
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.