Beets
The Flagship LST Hub on Sonic. From seamless staking to earning real yield on LST-focused liquidity pools, Beets is the ultimate destination for your liquid-staked tokens.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$200,000Minimum reward to discourage security researchers from withholding a bug report:
$20,000Rewards 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, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
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 20 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.
All vulnerabilities marked in the audits are not eligible for a reward.
Payouts are handled by the Beets DAO directly and are denominated in USD. However, payouts are done in USDC and BEETS.
Program Overview
The Flagship LST Hub on Sonic. From seamless staking to earning real yield on LST-focused liquidity pools, Beets is the ultimate destination for your liquid-staked tokens. For more information about Beets, please visit https://beets.fi/.
Please note that BeetsX is a friendly fork of Balancer V2 and V3. All balancer core contracts are covered by their bug bounty program
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.