Lido on Polkadot

Lido on Polkadot is a liquid staking solution for DOT. Lido lets users earn DOT staking rewards without needing to maintain infrastructure and enables them to trade staked positions, as well as participate in on-chain decentralized finance with their staked assets. Lido on Polkadot gives you:

• Liquidity through tokenization — no activation delays and the ability to sell your staked tokens or use them in decentralized finance;
• One-click staking — no complicated steps;
• Decentralized security and maximized staking performance — assets spread across the best performing validators from the whole network, that are not predefined. That is possible because of an algorithm based on provable data and decentralized oracles. You can learn more here.

For more information about Lido on Polkadot, please visit https://lido.fi/polkadot.

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. 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 24 hours
    • 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

• Web/App Medium:

  • 3 250 USD

• Web/App Low:

  • 1 000 USD

The following vulnerabilities are not eligible for a reward:

• All vulnerabilities found in https://github.com/Dedaub/audits/blob/main/Lido/Lido%20on%20Kusama%20audit%20Mar22.pdf
• All vulnerabilities found in https://github.com/mixbytes/audits_public/tree/master/Lido/Lido%20KSM
• Equal or duplicate issues submissions both for Lido on Kusama and Lido on Polkadot and vice versa since their codebase is very close.

Payouts are handled by the Lido on Polkadot team directly and are denominated in USD. However, payouts are done in LDO, ETH and DAI, with the choice of the ratio at the discretion of the team.

Smart Contract

Websites and Applications

All smart contracts of Lido on Polkadot can be found at https://github.com/mixbytes/lido-dot-ksm. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Lido on Polkadot that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical and High impacts.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)
• Equal or duplicate issues submissions both for Lido on Kusama and Lido on Polkadot and vice versa since their codebase is very close.

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty