> For the complete documentation index, see [llms.txt](https://docs.resupply.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resupply.finance/faq/bug-bounties.md).

# Bug Bounties

**Scope:** Issues which can lead to substantial loss of money, critical bugs like a broken live-ness condition or irreversible loss of funds.

**Disclosure policy:**

* Let us know as soon as possible upon discovery of a potential security issue.
* Provide us a reasonable amount of time to resolve the issue before any disclosure **to the public or a third-party.**

**Exclusions:**

* Already known vulnerabilities.
* Vulnerabilities in front-end code not leading to smart contract vulnerabilities.

**Eligibility:**

* You must be the first reporter of the vulnerability
* You must be able to verify a signature from same address
* Provide enough information about the vulnerability

**Bounty payout:**

| Likelihood     | Low Severity | Medium Severity | High Severity |
| -------------- | ------------ | --------------- | ------------- |
| Almost Certain | $10,000.00   | $50,000.00      | $250,000.00   |
| Possible       | $1,000.00    | $10,000.00      | $50,000.00    |
| Unlikely       | $1,000.00    | $1,000.00       | $10,000.00    |

**Contact:** <contact@resupply.fi>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.resupply.finance/faq/bug-bounties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
