# Bug Bounty

![](https://1112775216-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MZJYO091RF217n45Jl7%2F-Miw04itEB-g3jVYKgyD%2F-Miw09uFPPYbqXVBWOWA%2Fimage.png?alt=media\&token=c738a5ea-e766-43d0-8217-87d11ba45664)

Welcome to Lixir’s Bug Bounty Program. Our aim is to be the best, which is not possible without support from our community. Submit a bug here and earn a reward. The following are the conditions and rewards.

## Scope

Potential problems which can precipitate substantial loss of money, critical bugs like [deadlock](https://docs.oracle.com/javase/tutorial/essential/concurrency/deadlock.html) and [starvation](https://docs.oracle.com/javase/tutorial/essential/concurrency/starvelive.html), or permanent loss of funds.

## Disclosure Policy

Inform us as soon as possible of a potential vulnerability. Allow us a reasonable amount of time to fix the issue before disclosing to the public or a third-party.

## Eligibility

In order to be eligible, you must

1. be the first reporter of the vulnerability, 
2. be able to verify a signature from the same address,
3. and provide enough information about the vulnerability.

## Exclusions

Previously known vulnerabilities and vulnerabilities in front-end code not leading to smart contract vulnerabilities.

While testing for vulnerabilities, please take care not to: denial of service, spam, or phish the Lixir team.

## Judgement

The Lixir team is the sole and final arbiter to determine eligibility, exclusion, and reward. Rewards are decided on a case-by-case basis. Our reward scheme follows an approach similar to the [Ethereum Bug Bounty](https://bounty.ethereum.org/#faq).

## Reward

| Likelihood/Severity | Low           | Moderate        | Highly               |
| ------------------- | ------------- | --------------- | -------------------- |
| Low                 | Retweet       | 500$ in $LIX    | 1000$ in $LIX        |
| Moderate            | 500$ in $LIX  | 2000$ in $LIX   | 4500$ in $LIX        |
| Highly              | 1500$ in $LIX | 10,000$ in $LIX | up to 200k $ in $LIX |

## Submit a bug

For now join our [Discord](https://discord.gg/M68xC9c2Pk) or [Telegram](https://www.t.me/lixirfinance) and DM a CM or team member, or submit an e-mail to <info@lixir.finance>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lixir-finance.gitbook.io/lixir-doc/resources/security/bug-bounty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.