# Bug Bounty

The Hyperlend Bug Bounty Program invites security researchers and developers to help protect the protocol. We value the community’s role in ensuring the safety of user assets and the stability of our lending markets.

**Submission Process**

To qualify for a reward, please follow these steps:

1. Report: Write a detailed report including the potential impact and a technical description of the vulnerability.
2. PoC: Include a Proof of Concept or a set of reproduction steps (e.g., a Foundry test or Hardhat script).
3. Contact: Submit your report by opening a ticket in our Official Discord server: <https://discord.gg/HhbANtPPT6>

{% hint style="info" %}
First-to-Report: If multiple researchers find the same bug, only the first valid report will be rewarded.
{% endhint %}

Rewards: Payouts are made in USDC (or protocol-native tokens) on Hyperliquid based on the severity of the finding.

**Ineligibility Criteria**:

* Reports based on "theoretical" risks without a clear path to exploitation.
* Issues requiring physical access to a user’s device or "jailbroken" hardware.
* Vulnerabilities in third-party integrations (e.g., an external DEX where collateral is swapped) that Hyperlend does not control.
* UI/UX "papercuts" or minor spelling errors that do not impact security or financial logic.
* Market risks inherent to DeFi (e.g., loss of collateral value due to standard market volatility).

**Classification & Rewards**

Rewards are determined by the Hyperlend team based on the Impact and Likelihood.


---

# 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://docs.hyperlend.finance/developer-documentation/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.