
Starknet Staking
Bounty Range
$1,000 - $100,000
external program
Staking on Starknet involves locking STRK tokens, and/or BTC wrappers in the staking protocol, in order to contribute to network security and performance. Users can either stake directly or delegate their tokens to others (BTC can only be delegated), with staking rewards based on their level of participation and contribution.
For more information about Starknet Staking, please visit https://docs.starknet.io/staking/overview/
Starknet Staking provides rewards in USDC or STRK on Ethereum, denominated in USD.
Smart Contract
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000.
Minimum reward to discourage security researchers from withholding a bug report: $15,000
Payouts: Payouts are handled by the StarkWare team directly and are denominated in USD. However, payments are done in USDC or STRK, at StarkWare's discretion.
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.
Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Known issues include:
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria.
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: