StakeStone
Bounty Range
$5,000 - $300,000
external program
StakeStone
StakeStone is committed to building the first stable, yield-bearing liquid ETH/BTC, powered by an adaptive staking network that supports various risk-free consensus layers with native assets. Yield opportunities are optimized through adaptable underlying strategies using an on-chain proposal mechanism called OPAP, which seamlessly redistributes omnichain liquidity across ecosystems and protocols. Backed by leading investors such as Binance Labs, OKX Ventures, SevenX, HashKey Capital & HashKey Cloud, Amber Group, Cobo, Nomad Capital, Symbolic Capital, Dao5, and Bankless Ventures.
For more information about StakeStone, please visit https://stakestone.io/
StakeStone provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract - Critical
Smart Contract - High
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $300,000.
Minimum reward to discourage security researchers from withholding a bug report: $20,000
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 300,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 20,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 5,000 to USD 20,000, depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Reward Payment Terms
Payouts are handled by the StakeStone team directly and are denominated in USD. However, payments are done in USDC on ETH.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
KYC Requirement
Immunefi will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Primacy of Rules
StakeStone adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Previous Audits
StakeStone's completed audit reports can be found at https://docs.stakestone.io/stakestone/additionals/audits-and-security. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Immunefi Standard Badge
By adhering to Immunefi's best practice recommendations, StakeStone has satisfied the requirements for the Immunefi Standard Badge.
Proof of concept is always required for all severities.
Category 3: Approval Required
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, including considerations for: