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:

Immunefi - Immunefi Vulnerability Severity Classification System - v2.2 | Immunefiimmunefi

---

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