# Bug Bounty: Join the Hunt

**Intro**: In our quest to build a top-notch, secure, and robust Kuro ecosystem, we understand the importance of community involvement. We're introducing our Bug Bounty program to engage our skilled community members in the hunt for bugs and vulnerabilities. Join the fun, contribute to the project, and get rewarded for your efforts!

**Step 1**: Identify the Bug Start by exploring the Kuro ecosystem, including smart contracts, web applications, and any other components. Keep an eye out for any security vulnerabilities, glitches, or bugs that could impact the system's stability or user experience.

**Step 2**: Report It Found a bug? Great! Shoot us an email at <bugs@kurotoken.com> with the following details:

* A brief description of the bug
* Steps to reproduce the issue
* Your proposed solution (if you have one)
* Any additional information or screenshots that can help us understand the problem better

**Step 3:** Get Rewarded Our team will review your submission and assess the severity of the bug. If your report leads to a confirmed fix, you'll earn a reward based on the bug's impact. The bigger the bug, the better the bounty!

*Disclaimer: Please note that we reserve the right to evaluate each submission on a case-by-case basis. Submitting a bug report does not guarantee a reward. Ensure that your report is accurate, concise, and complete to increase your chances of receiving a bounty.*


---

# 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.kurotoken.com/help/bug-bounty-join-the-hunt.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.
