Lido
Lido is a liquid staking solution for Ethereum, backed by industry-leading staking providers and community stakers. It allows users to stake their ETH without locking up assets or maintaining infrastructure, while still participating in on-chain activities.
Triaged by Immunefi
PoC Required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$2,000,000Minimum reward to discourage security researchers from withholding a bug report:
$50,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3. This is a simplified 4-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 web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.
Smart Contracts Rewards Breakdown
Critical
-
Loss of user funds:
- When a minimum of 1% of assets is at risk
- Reward: Minimum 100,000 USD, Maximum 2,000,000 USD
-
Loss of non-user funds (e.g., treasury):
- When a minimum of 1% of assets is at risk
- Reward: Minimum 50,000 USD, Maximum 1,000,000 USD
High
- When a minimum of 1% of assets is at risk
- Reward: Minimum 20,000 USD, Maximum 250,000 USD
Medium
- When a minimum of 1% of assets is at risk
- Reward: Minimum 5,000 USD, Maximum 50,000 USD
Low
- Reward: 1,000 USD
Web/App Rewards Breakdown
Critical
- Reward: Minimum 50,000 USD, Maximum 100,000 USD
High
- Reward: Minimum 5,000 USD, Maximum 50,000 USD
Medium
- Reward: Minimum 1,000 USD, Maximum 5,000 USD
Low
- Reward: 500 USD
- (Smart contracts Out Of Scope) Rewards on partner contracts are paid at contributors discretion.
- (Web apps) Reports regarding domains not listed under the scope section are paid at contributors discretion.
Payouts are handled by the Lido contributors directly and are denominated in USD. Payouts can be done in USDC, USDS, DAI, or USDT, at the decision of the bug bounty hunter.
Program Overview
Lido is a liquid staking solution for Ethereum, backed by industry-leading staking providers and community stakers. It allows users to stake their ETH without locking up assets or maintaining infrastructure, while still participating in on-chain activities.
Lido aims to solve the key challenges of early Ethereum staking — illiquidity, immovability, and limited accessibility — by making staked ETH liquid and enabling participation with any amount. This helps strengthen the security of the Ethereum network.
For more information about Lido, please visit Lido.fi.
The bug bounty program covers its smart contracts and applications, focusing on preventing loss of user funds, some types of denial of service attacks, governance hijacks, data breaches, and data leaks.
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
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Automated testing of services that generates significant amounts of traffic
- Any denial of service attacks that are executed against project assets
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Attempting phishing or other social engineering attacks against our contributors and/or stakers
- Any testing with pricing oracles or third-party smart contracts
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any other actions prohibited by the Immunefi Rules - https://immunefi.com/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.