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

# Bug Bounty

At Secure3, we recognize that maintaining security is a continuous endeavour. To support projects in fortifying their defences, we provide a robust Bug Bounty solution that enables ongoing identification and remediation of vulnerabilities.

{% hint style="success" %}
[Contact us](https://tally.so/r/mOlevY) if you're interested in launching a bug bounty for your project.
{% endhint %}

### Key Benefits of Our Bug Bounty Program

* **Flexible Reward Options**: 
  * Projects can issue rewards in your native tokens, aligning incentives with the project's ecosystem and encouraging active participation from security experts.
* **Access to a Skilled Auditor Community**: 
  * Engage with a diverse community of seasoned auditors and security experts, bringing a wealth of expertise to identify and mitigate vulnerabilities.
* **Continuous Improvement**: 
  * Our ongoing assessments enable prompt detection of new vulnerabilities, ensuring your project remains adaptable to evolving security challenges.

### Special Offer for Audit Contest Sponsors

For projects that sponsor a Secure3 Audit Contest, we are excited to provide a **FREE Bug Bounty** as an added benefit. This initiative includes all the general advantages listed above, along with:

* **Zero Take Rate**: Enjoy a **0% take rate** by Secure3, allowing you to maximize your budget and ensure all rewards go directly to the auditors.
* **Continuous Access**: Gain free access to our community of auditors, ensuring ongoing support and expertise in identifying and addressing potential vulnerabilities.


---

# 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.secure3.io/solutions/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.