Lido
Lido is a liquid staking solution for Ethereum backed by industry-leading staking providers. Lido lets users stake their ETH - without locking assets or maintaining infrastructure - whilst participating in on-chain activities, e.g. lending.
PoC required
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 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 Breakdowns
-
Smart Contracts Critical:
- Loss of user funds:
- 1% of assets at risk, minimum 100 000 USD, maximum 2 000 000 USD
- Loss of non-user funds (e.g. treasury):
- 1% of assets at risk, minimum 50 000 USD , maximum 1 000 000 USD
- Loss of user funds:
-
Smart Contracts High:
- 1% of assets at risk when attack persists for 1 month
- minimum 20 000 USD, maximum of 400 000 USD
- 1% of assets at risk when attack persists for 1 month
-
Smart Contracts Medium:
- 1% of assets at risk when attack persists for 1 month
- minimum 5 000 USD, maximum 100 000 USD
- 1% of assets at risk when attack persists for 1 month
-
Smart Contracts Low:
- 2 000 USD
Web/App Rewards Breakdowns
-
Web/App Critical:
- 40 000 USD
-
Web/App High:
- 7 500 USD
- If attack can modify the transaction users approve so it sends funds to the wrong address: then this reward increases to a total of 40 000 USD
-
Web/App Medium:
- 3 250 USD
-
Web/App Low:
- 500 USD
Payouts are handled by the Lido team directly and are denominated in USD. Payouts can be done in ETH, DAI, RAI, or LDO, at the decision of the bug bounty hunter.
Program Overview
Lido is a liquid staking solution for Ethereum backed by industry-leading staking providers. Lido lets users stake their ETH - without locking assets or maintaining infrastructure - whilst participating in on-chain activities, e.g. lending.
Lido attempts to solve the problems associated with initial Ethereum staking - illiquidity, immovability and accessibility - making staked ETH liquid and allowing for participation with any amount of ETH to improve security of the Ethereum network.
For more information about Lido, please visit Lido.fi.
The bug bounty program covers its smart contracts and apps and is focused on the prevention of loss of user funds, denial of service, governance hijacks, data breaches, and data leaks.
KYC not required
No KYC information is required for payout processing.
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.