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

# Crus Vulnerability Bounty Scheme

<figure><img src="/files/5B5wqs5jXiXiEfC4FjVd" alt=""><figcaption></figcaption></figure>

Program Objectives:

1. Identify Vulnerabilities: The primary objective of the bounty scheme is to discover any vulnerabilities or weaknesses in the CrusSwap platform. This includes both technical and logical flaws that may pose a risk to user data, transactions, or overall system stability.
2. Responsible Disclosure: We encourage ethical hacking practices and responsible disclosure. If you discover a vulnerability, we kindly request that you report it to us directly, allowing us the opportunity to investigate and address the issue before making it public.
3. Rewards and Recognition: As a token of appreciation for your contributions, we offer monetary rewards based on the severity and impact of the reported vulnerabilities. In addition, we recognize the efforts of ethical hackers who help us enhance the security of CrusSwap.

Scope of the Program: The bounty scheme covers various aspects of CrusSwap, including but not limited to:

* Smart contract vulnerabilities
* Front-end security flaws
* Improper access control mechanisms
* Data leakage or privacy issues
* Malicious or fraudulent activities

Reporting Vulnerabilities: To participate in the Crus Vulnerability Bounty Scheme, follow these steps:

1. Conduct a thorough assessment of CrusSwap for potential vulnerabilities.
2. Document your findings, including clear steps to reproduce the issue and any supporting evidence.
3. Submit your report to our dedicated vulnerability reporting platform, ensuring you provide sufficient details for our team to reproduce and validate the vulnerability.
4. Allow us a reasonable timeframe to investigate and address the reported vulnerability before making it public.

Rewards and Recognition: Rewards for reported vulnerabilities will be determined based on severity, impact, and the quality of the submission. The following factors are taken into consideration:

* Criticality and potential exploitability of the vulnerability
* Impact on user data and assets
* Quality and thoroughness of the report
* Novelty and uniqueness of the vulnerability

We value your contributions and understand the importance of recognizing your efforts. Therefore, we ensure that all eligible reports are acknowledged and rewarded accordingly.

Conclusion: The Crus Vulnerability Bounty Scheme aims to foster a secure and resilient ecosystem for CrusSwap users. By collaborating with security researchers, ethical hackers, and the wider community, we strive to identify and address vulnerabilities, ensuring a safer and more reliable DeFi experience.

Your contributions are invaluable, and we appreciate your commitment to enhancing the security of CrusSwap. Together, let's build a stronger and more secure future for decentralized finance.

For more information, guidelines, and submission details, please visit our dedicated page at \[<https://forms.gle/fKcrVrGJwpNQC4rd6>].


---

# 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:

```
GET https://crus.gitbook.io/crus/trouble-shooting/crus-vulnerability-bounty-scheme.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.