04 November 2021
Live since
No
KYC required
$200,000
Maximum bounty

Program Overview

Lixir Finance is a concentrated liquidity manager designed to automate liquidity management and optimize returns. Lixir sets out to integrate the next generation of Automated Market Makers (AMMs) that offer the ability to provide liquidity in a tight range, such as Uniswap V3. Concentrated liquidity allows liquidity providers to greatly increase the revenue from

Liquidity Provider fees (LP fees), but there are trade-offs. Lixir is designed to simplify and optimize these trade-offs through a user-friendly interface that hides all the complexity that concentrated liquidity introduces.

For more information about Lixir, please visit https://lixir.finance/
This bug bounty program is focused on their smart contracts and app 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 by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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 Critical Smart Contract bug reports require a PoC, and a suggestion for a fix for Medium, High and Critical bugs is required to be eligible for a reward.

Critical smart contract vulnerabilities are capped at 15% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.

Payouts are handled by the Lixir team directly and are denominated in USD. However, payouts are done in Lix.

Smart Contract

Critical
Level
Up to USD $200,000
Payout
PoC Required
High
Level
USD $10,000
Payout
Medium
Level
USD $1,500
Payout

Assets in scope

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

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

  • Loss of user funds staked (principal) by freezing or theft
    Critical
    Impact
  • Loss of governance funds
    Critical
    Impact
  • Vote manipulation
    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

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