> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/developers/resources/bug-bounty.md).

# Bug bounty

The route for reporting a Leather vulnerability.

Leather's bug bounty runs on Immunefi. The [program page](https://immunefi.com/bug-bounty/leather/information/) is the authoritative source for scope, severity classification, reward tiers, and terms. Read it before you test or submit.

{% hint style="info" %}
Do not report security vulnerabilities in GitHub issues, Discord, Telegram, or on social media. Only reports submitted through Immunefi are considered for a reward, and public disclosure of an unpatched vulnerability breaches the program terms.
{% endhint %}

### Where to go

* [Information](https://immunefi.com/bug-bounty/leather/information/): rewards, payout process, KYC, and the required report template.
* [Scope](https://immunefi.com/bug-bounty/leather/scope/): assets in scope, impacts in scope, and the out-of-scope list.

<a href="https://bugs.immunefi.com/dashboard/new-submission" class="button primary">Submit a report on Immunefi</a>

### Issues that belong elsewhere

Vulnerabilities in the Stacks protocol itself are outside this program. Stacks blockchain and core contract issues go to the [Stacks program on Immunefi](https://immunefi.com/bug-bounty/stacks/information/).

### Reporting without a reward claim

To disclose a finding without claiming a bounty, send it to <security@leather.io>. Reports sent there stay outside the bug bounty program and are not considered for payment. The prohibitions on mainnet testing, social engineering, and public disclosure of an unpatched vulnerability still apply.


---

# 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://leather.gitbook.io/developers/resources/bug-bounty.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.