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

# Bug Bounty Program

The Copycat bug bounty program covers our smart contracts, it is focused on the prevention of loss of user funds. If a bug is found.

**Smart Contracts and Blockchain** 

Find bugs in production smart contracts to earn the highest paying bounties. 

| Security Level | Bounty                                    |
| -------------- | ----------------------------------------- |
| Critical       | up to USD $5,000 (50% of economic damage) |
| High           | USD $2,000                                |
| Medium         | USD $1,000                                |
| Low            | USD $500                                  |

Reports must include a proof of concept either in the form of a smart contract or transaction. 

Payouts are handled by the **Copycat** team directly and are denominated in USD. Payouts are done in **COPYCAT** or **BUSD**, at the discretion of the **Copycat** team.


---

# 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://docs.copycat.finance/community-1/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.