Lyra-logo

Lyra

Lyra V2 is a self-custodial protocol layer built to enable the trading of derivative products in a permissionless way.

Optimism
Defi
DEX
Options
Perpetuals
Solidity
Maximum Bounty
$50,000
Live Since
23 August 2021
Last Updated
18 November 2024
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Target
Name
DepositModule
Added on
11 January 2024
Target
Name
Matching
Added on
11 January 2024
Target
Name
TradeModule
Added on
11 January 2024
Target
Name
TransferModule
Added on
11 January 2024
Target
Name
WithdrawalModule
Added on
11 January 2024
Target
Name
DutchAuction
Added on
11 January 2024
Target
Name
CashAsset
Added on
11 January 2024
Target
Name
InterestRateModel
Added on
11 January 2024
Target
Name
SecurityModule
Added on
11 January 2024
Target
Name
StandardManager
Added on
11 January 2024
Target
Name
StandardManagerViewer
Added on
11 January 2024
Target
Name
LyraSpotFeed
Added on
11 January 2024

Impacts in Scope

Severity
Critical
Title

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

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Theft of unclaimed yield

Severity
Critical
Title

Permanent freezing of unclaimed yield

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Freezing of unclaimed yield

Severity
High
Title

Temporary freezing of funds for any amount of time

Severity
Medium
Title

Unable to call smart contract

Severity
Medium
Title

Smart contract gas drainage

Severity
Low
Title

Smart contract fails to deliver promised returns

Out of scope

Program's Out of Scope information
  • Best practice critiques
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers