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

# Bug Bounty

HyperLink's bug bounty program: scope, severity-based rewards, and how to responsibly report vulnerabilities affecting funds, privacy, or trading integrity.

Report vulnerabilities that could affect HyperLink user funds, privacy, or trading integrity.

## Scope

In scope:

* Core deployed HyperLink contracts.
* Production API issues that can affect funds, privacy, or trading integrity.

Out of scope:

* Website or UI-only issues with no security impact.
* Documentation issues.
* Spam, denial-of-service testing, and generic rate-limit findings.
* Social engineering, phishing, or physical attacks.
* Third-party outages or vulnerabilities outside HyperLink's control.
* Issues that require stolen keys, leaked credentials, or privileged access.

## Rewards

| Severity | Reward                                               |
| -------- | ---------------------------------------------------- |
| Critical | 10% of funds at risk, up to $50,000, minimum $10,000 |
| High     | $2,500 to $8,000                                     |
| Medium   | $750                                                 |
| Low      | $250                                                 |

Severity and reward are determined by practical impact. Duplicate reports are paid to the first valid reporter.

## Rules

* Include a clear impact statement and reproduction steps.
* Include a runnable proof of concept for Critical and High reports.
* Do not exploit an issue beyond what is needed to prove impact.
* Do not move user funds or access user data.
* Do not publicly disclose the issue before HyperLink has remediated it.

## Submit a Report

Email reports to <bugbounty@hyperlink.xyz>.


---

# 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.hyperlink.xyz/security/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.