23 August 2021
Live since
No
KYC required
$50,000
Maximum bounty
08 April 2024
Last updated

Program Overview

Lyra V2 is a self-custodial protocol layer built to enable the trading of derivative products in a permissionless way. The component of the Lyra V2 stack covered by this bug bounty program is the Lyra Protocol: A protocol that enables the margining and settlement of perpetuals, options and spot.

For more information about Lyra, please visit https://www.lyra.finance/.

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 High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. There is a maximum reward of USD 50 000, but more could be paid out at the discretion of the team.

Any vulnerability already disclosed in the audits that have been performed are not able to receive a reward.

Issues identified in previous audit reports may not be eligible for payout.

To be eligible for reward, impact from table below must be demonstrated where all thefts must be profitable and all freezing must be reasonably priced for the impact.

Payouts up to USD 50,000 are handled by the Lyra team directly and are denominated in USD. However, payouts are done in USDC or ETH, at the discretion of the team.

Smart Contract

Critical
Level
USD $5,000 to USD $50,000
Payout
PoC Required
High
Level
USD $5,000
Payout
PoC Required
Medium
Level
USD $2,000
Payout
Low
Level
USD $500
Payout

Assets in scope

Contracts in scope are found on the Lyra Chain (https://rpc.lyra.finance; chainId: 957; https://explorer.lyra.finance/), as well as any libraries they inherit.

Code for these contracts can be found in the following repositories: https://github.com/lyra-finance/v2-core https://github.com/lyra-finance/v2-matching https://github.com/lyra-finance/lyra-utils

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contract

  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
    Critical
    Impact
  • Permanent freezing of funds
    Critical
    Impact
  • Theft of unclaimed yield
    Critical
    Impact
  • Permanent freezing of unclaimed yield
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds for any amount of time
    High
    Impact
  • Unable to call smart contract
    Medium
    Impact
  • Smart contract gas drainage
    Medium
    Impact
  • Smart contract fails to deliver promised returns
    Low
    Impact

Out of Scope & Rules

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
  • Centralization risks

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