Carbon DeFi by Bancor
The Carbon Defi Bug Bounty aims to incentivize responsible disclosures of any bugs in the Carbon Defi smart contracts. Starting with the official Beta launch, the carbon-contracts repository are subject to the bounty program.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of user or protocol funds other than unclaimed yield
Protocol insolvency
Permanent freezing of funds
Smart contract unable to operate due to lack of token funds
Block stuffing for profit
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Unbounded gas consumption
Theft of gas
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
The following are not within the scope of the Program:
- Bugs in any third party contract or platform that interacts with Carbon Defi.
- Vulnerabilities already reported and/or discovered in contracts built by third parties on Carbon Defi. We reserve the right to keep private previous bug disclosures.
- Any previously reported bugs.
- Best practice critiques
- Bugs in any third party contract or platform that interacts with the Carbon Defi protocol (Note that oracle manipulation and flash loan attacks are included in the bounty)
Other Terms
By submitting your report, you grant the Bprotocol Foundation any and all rights, including intellectual property rights, needed to validate, mitigate, and disclose the vulnerability. All reward decisions, including eligibility for and amounts of the rewards and the manner in which such rewards will be paid, are made at the sole discretion of the Bprotocol Foundation. The terms and conditions of the Carbon Defi Bug Bounty Program may be altered at any time. The above scope, terms and rewards of the program are at the sole discretion of the Bprotocol Foundation.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers