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

# Bug Bounty

## Program Overview

The classification of severity levels is determined by [Immunefi Vulnerability Severity Classification System](https://immunefi.com/severity-updated/). It is important to note that these levels are merely suggestions and each bug bounty submission will be individually assessed.

## Invalid Bug Bounties

The following are not covered by the bug bounty program:

* Incidents where the reporter has caused harm by exploiting the vulnerability themselves.
* Vulnerabilities that can only be exploited by utilizing leaked keys or credentials.
* Vulnerabilities that require access to privileged addresses such as governance or admin addresses.
* Issues caused by incorrect data supplied by external oracles (however, oracle manipulation or flash loan attacks are still in scope)
* Situations where there is a lack of liquidity.
* Errors made by third-party off-chain bots (e.g. bugs in an arbitrage bot running on the smart contracts)
* Suggestions for best practice or critiques.
* Sybil attacks.


---

# 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://whitepaper.opz.io/misc/bug-bounty.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.