Lido on Polygon
Lido on Polygon, developed in collaboration with Shard Labs, is a liquid staking solution for MATIC.
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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Smart Contract bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
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:
- 1 000 USD
All vulnerabilities marked in the https://github.com/lidofinance/polygon-contracts/tree/main/audits are not eligible for a reward.
Payouts are handled by the Lido on Polygon 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 on Polygon, developed in collaboration with Shard Labs, is a liquid staking solution for MATIC.
MATIC holders can now seamlessly earn staking rewards on their tokens without the need for complex infrastructure or locked/illiquid tokens. Stake your MATIC with Lido to receive stMATIC tokens which can be traded, transferred and used across the growing Polygon DeFi space.
For more information about Lido, the parent project, please visit their main bug bounty program at https://immunefi.com/bounty/lido/.
For more information about Lido on Polygon, please visit https://lido.fi/polygon.
This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:
- Any governance voting result manipulation
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
- Permanent freezing of funds
- Miner-extractable value (MEV)
- Insolvency
- Theft of unclaimed yield
- Ability to execute system commands
- Extract Sensitive data/files from the server such as /etc/passwd
- Stealing User Cookies
- Taking Down the application/website
- Signing transactions for other users
- Redirection of user deposits and withdrawals
- Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
- Wallet interaction modification resulting in financial loss
- Direct theft of user funds
- Tampering with transactions submitted to the user’s wallet
- Submitting malicious transactions to an already-connected wallet
Vulnerability reported to any Lido project is considered as reported to each Lido Bug Bounty program. Reports of the same vulnerability to multiple Lido Bug Bounty programs will be considered as a single report, when reward is calculated. List of Lido programs:
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.