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

# Bug Bounty

MegaTAO takes the security of user funds seriously. We encourage responsible disclosure of any vulnerabilities discovered in the protocol.

## Scope

The following are in scope for the bug bounty program:

* **Smart contracts:** All deployed MegaTAO contracts on Bittensor EVM
* **Oracle contracts:** Price oracle and related infrastructure
* **Economic vulnerabilities:** Attacks that could drain funds, manipulate prices, or cause incorrect liquidations

## Out of Scope

* Frontend/UI issues that do not affect funds
* Social engineering attacks
* Denial-of-service attacks on RPC infrastructure
* Issues in third-party dependencies outside our control
* Known issues already documented in audit reports

## How to Report

If you discover a vulnerability:

1. **Do not** disclose it publicly
2. **Do not** exploit it on mainnet
3. Email details to **<info@megatao.com>** with the subject line "Security Vulnerability Report"
4. Include a clear description, reproduction steps, and potential impact
5. Allow reasonable time for the team to investigate and remediate

## Response Timeline

* **Acknowledgment**: Within 48 hours of report
* **Initial assessment**: Within 5 business days
* **Remediation**: Depends on severity; critical issues are prioritized immediately

## Rewards

Rewards are determined on a case-by-case basis depending on the severity and impact of the vulnerability. Critical vulnerabilities that could result in loss of user funds receive the highest rewards.

| Severity | Description                                            | Reward Range |
| -------- | ------------------------------------------------------ | ------------ |
| Critical | Direct loss of user funds or protocol insolvency       | Case-by-case |
| High     | Significant economic impact or privilege escalation    | Case-by-case |
| Medium   | Limited economic impact or incorrect state transitions | Case-by-case |
| Low      | Minor issues with no direct financial impact           | Case-by-case |

## Responsible Disclosure

We ask all researchers to follow responsible disclosure practices. We will not take legal action against researchers who report vulnerabilities in good faith and follow the guidelines above.

***

*Thank you for helping keep MegaTAO secure. Reach out to <info@megatao.com> with any questions about this program.*


---

# 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.megatao.com/audits/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.