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

# Bug Bounty Program

We won't be reinventing the wheel for the classification of issues, and this page was inspired by the great Immunefi™️  `vulnerability-severity-classification-system-v2-2` that can be found here:

{% embed url="<https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/>" %}

***

This is a simplified 5-level scale, which is further categorised by websites and apps, smart contracts and blockchains. This simplified scale encompasses everything from the consequences of exploitation to the privilege required, and to the likelihood of a successful exploit.

All smart contract bug reports must come with a PoC to be considered for a reward.

Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected, in addition to the PR and brand considerations, at the discretion of the team. However, there is a minimum of **USD 50,000** for Critical Bug reports listed below.

Payouts are handled by the **Adrena** team directly and are denominated in USD. However, payouts are done in **ADX.**

***

**Only the smart contract is in scope for this bug bounty - Below is the scope**

***

| Critical scope - Up to 250k USDC (minimum 50k)                                           |
| ---------------------------------------------------------------------------------------- |
| Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield |
| Permanent freezing of funds                                                              |
| Protocol Insolvency                                                                      |

| High scope - Up to 15k USDC                       |
| ------------------------------------------------- |
| Temporary freezing of funds excluding DOS attacks |

***

### Out of scope

The following vulnerabilities are excluded from the rewards for this bug bounty program:

Attacks that the reporter has already exploited themselves leading to damage. Attacks requiring access to leaked keys/credentials. Attacks requiring access to privileged addresses (governance, strategist)

**Smart Contracts and Blockchain**

* Incorrect data supplied by third party oracles
  * Not to exclude oracle manipulation/flash loan attacks
* Basic economic governance attacks (e.g. 51% attack)
* Lack of liquidity
* Best practice critiques
* Sybil attacks

### The following activities are prohibited by this bug bounty program:

* Any testing with mainnet or public testnet contracts. All testing should be done on private testnets.
* Any testing with pricing oracles or third-party smart contracts.
* Attempting phishing or other social engineering attacks against our employees and/or customers.
* Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks).
* Any denial-of-service(DoS) attacks
* Automated testing of services that generate significant amounts of traffic
* Public disclosure of an unpatched vulnerability in an embargoed bounty


---

# 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 dynamically by asking a question.

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

```
GET https://adrena.gitbook.io/adrena/about-adrena/bug-bounty-program.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.