Lossless

Lossless is the first DeFi hack mitigation tool for token creators. Lossless Protocol freezes fraudulent transactions based on a set of fraud identification parameters and returns stolen funds back to the owner’s account.

For more information about Lossless, please visit https://lossless.cash/.

This bug bounty program is focused on their smart contracts and is focused on preventing:

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Theft of governance funds
• Governance activity disruption

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 Low, Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward.

Issues that were already found here https://www.certik.com/projects/lossless are not eligible for a reward.

Payouts are handled by the Lossless team directly and are denominated in USD. However, payouts are done in USDC or USDT, with the choice of the ratio at the discretion of the team.

All smart contracts of Lossless can be found at https://github.com/Lossless-Cash/lossless-v2. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

These accepted impacts are then based on the severity classification system of this bug bounty program. When submitting a bug report, please select the severity level you feel best corresponds to the severity classification system as long as the impact itself is one of the listed items.

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)

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

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