All smart contracts of Lido on Polygon can be found at [https://github.com/lidofinance/polygon-contracts/tree/main/contracts](https://github.com/lidofinance/polygon-contracts/tree/main/contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. In the Github link in the Assets in Scope table, only Exact Match Verified smart contracts are considered as in-scope of the bug bounty program. 


Lido on Polygon, developed in collaboration with Shard Labs, is a liquid staking solution for MATIC.

Any governance voting result manipulation

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Miner-extractable value (MEV)

Permanent freezing of funds

Insolvency

Theft of unclaimed yield

Ability to execute system commands

Extract Sensitive data/files from the server such as /etc/passwd

Taking Down the application/website

Stealing User Cookies

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

Tampering with transactions submitted to the user’s wallet

Direct theft of user funds

Submitting malicious transactions to an already-connected wallet

Permanent freezing of unclaimed yield

Temporary freezing of funds for a minimum of 24 hours

Spoofing content on the target application (Persistent)

Users Confidential information disclosure such as Email

Subdomain Takeover without financial loss (applicable for subdomains with no addresses published)

Privilege escalation to access unauthorized functionalities

Smart contract unable to operate due to lack of funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Changing details of other users without direct financial impact (CSRF)

Third-Party API keys leakage that demonstrates loss of funds or modification on the website

Redirecting users to malicious websites (Open Redirect)

Broken Link Hijacking

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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

  - Smart Contracts High:
    - 1% of assets at risk when attack persists for 1 month
      - minimum 20 000 USD, maximum of 400 000 USD

  - Smart Contracts Medium:
    - 1% of assets at risk when attack persists for 1 month
      - minimum 5 000 USD, maximum 100 000 USD

  - 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](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.__

Lido on Polygon

Resources & Documentation