Beethoven X — Bug Bounty Program
Dear Friends and Fellow Ludwigs,
When it comes to DeFi the most important base layer and one which is often overlooked by the masses is security. Without a bulletproof foundation that has been put through rigorous testing, users are exposed to elevated risk factors that compromise safety and adoption. By prioritizing security and investing in initiatives like bug bounties / smart contract audits protocols can actively combat many of the security risks inherent to the industry.
Beethoven X is deeply committed to providing the safest possible environment for its users and has put in a notable effort towards making sure the platform is battle tested and secure.
As an official friendly fork of Balancer we are exposed to many of the same smart contract vulnerabilities and as such we have committed, where we can, to support any of the initiatives they have put forward to combat malicious activity. We currently contribute towards one of the largest Bug Bounties (BLabs) in DeFi an effort to mitigate the risk posed by smart contact vulnerabilities.
Balancer Bug Bounties | Immunefi
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity…
On top of the efforts made by Balancer, we have also decided to run our own Bug Bounty initiative. Our protocol uses more than the contracts that are covered by the Balancer program and as such it only makes sense for us to further incentive the security of the platform. The goal is to incentivise ethical hackers across the globe to seek out / expose vulnerabilities in smart contracts on the platform, consequently driving the evolution of the security layers on the protocol.
The bug bounty will be launched in partnership with Immunefi and the details of the bounty are detailed below.
So, without further ado, we introduce the Beethoven X Bug Bounty.
Beethoven X aims to be a one-stop decentralized investment platform for DeFi.
We leverage the best in breed DeFi protocols to offer novel decentralized investment strategies. Built on Balancer V2, Beethoven X is the first next-generation AMM protocol on Fantom and Optimism.
For more information about Beethoven X, please visit https://beets.fi/.
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, smart contracts, focusing on the impact of the vulnerability reported.
Critical USD 50 000 to USD 500 000
High USD 5 000 to USD 20 000
Websites and Applications
Critical USD 20 000
High USD 10 000
Medium USD 2 000
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix 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. However, there is a minimum reward of USD 50 000.
High severity smart contract vulnerabilities are also further capped at 10% of economic damage, primarily taking into consideration funds at risk. However, there is a minimum reward of USD 5 000.
Payouts are handled by the Beethoven X team directly and are denominated in USD. However, payouts are done in USDC and BEETS.
Assets in Scope
All smart contracts of Beethoven X can be found at:
Repositories TypeScript Updated 1 MIT 47 3 Sep 15, 2022 TypeScript 0 MIT Updated 5 2 Sep 15, 2022 TypeScript Updated 6…
However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If an impact can be caused to any other asset managed by Beethoven X that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
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.
- Direct theft of any user funds, other than unclaimed yield, in excess of gas costs or swap fees
- Permanent freezing of funds in excess of gas costs or swap fees
- Theft of unclaimed yield
- Permanent freezing of unclaimed yield
- Temporary freezing of funds for a minimum period of 1 hour in excess of gas costs or swap fees
Websites and Applications
- Direct theft of user funds
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
- Execute arbitrary system commands
- Taking down the application/website
- Domain takeover
- Retrieve sensitive data/files from a running server such as /etc/shadow and database passwords (this does not include non-sensitive environment variables, open source code, or usernames)
- Redirecting users to malicious websites (Open Redirect)
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
- Centralization risks
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude persistent plain text injection
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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
Our contribution to the bug bounty program directly enhance our efforts to safeguard user funds and promotes a healthy environment that is well suited for sustainable, long-term growth.
Security is essential. No compromises.
We will continue to support any endeavours that lead to a safer user experience and strive for excellence across the board.