Bug Bounty Program
Furucombo Bug Bounty Program
The Furucombo team combines the merits of every kind of DeFi protocol to create the most comprehensive DeFi aggregator platform on Ethereum & Polygon. The structure of Furucombo is composed of proxy contracts and handler contracts. The security of our system is of paramount importance to us. While we continue conducting professional audits for the whole system, a bug bounty program is necessary to also ensure the platform’s safety.
This program is intended to work with independent security researchers across the globe and set out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what users can expect from us in return. Should you encounter a security vulnerability in one of our products, we want to hear from you. We believe that the Furucombo ecosystem will be further bolstered with support from our community.
This bug bounty program is focused on smart contracts and is focused on preventing:
- Loss of user funds during a transaction by freezing or theft
- Loss of user funds by theft of approved smart contracts
- Theft of unclaimed yield
- Freezing of unclaimed yield unable to call smart contract
- Smart contract gas drainage
- Smart contract failure to deliver promised returns
- Interaction with unauthorized handler logic
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.
All Low, Medium, High and Critical Smart Contract bug reports require a PoC to be eligible for a reward.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.
All vulnerabilities found in https://github.com/dinngodev/furucombo-contract/tree/master/audit are not eligible for a reward.
FURUCOMBO requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name and Email Address. The collection of this information will be done by the FURUCOMBO team.
Payouts are handled by the FURUCOMBO team directly and are denominated in USD. However, payouts are done in ETH, DAI, USDC and COMBO, with the choice of the ratio at the discretion of the team.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.
The following vulnerabilities are not eligible for a reward:
- All vulnerabilities found in https://github.com/dinngodev/furucombo-funds-contract/tree/master/audit
Payouts are handled by the Furucombo Funds team directly and are denominated in USD. However, payouts are done in ETH, DAI, USDC and COMBO, with the choice of the ratio at the discretion of the team.
For more information about the scope or eligible contracts, please visit https://immunefi.com/bounty/furucombo/.
For more information about the scope or eligible contracts, please visit https://immunefi.com/bounty/furucombofunds/.
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)
- 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
- Centralization risks
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
Other issues found outside of the locations mentioned above, such as https://furucombo.app/, will be considered on a case by case basis. Please reach out to the Furucombo development team on Discord for clarification.
Breaking or neglecting any of the rules mentioned above will be a violation of the Furucombo Bug Bounty Program. Furucombo reserves the right to modify or cancel the program at Furucombo’s sole discretion and at any time.
Last modified 9mo ago