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

# Bug Bounty

## Bug Bounty Program

In addition to these measures, we offer a bug bounty for the core components of the ChainGPT ecosystem, as outlined in the Scope section below. This program helps us ensure that our software meets the highest standards and minimizes the risk of users losing funds.

#### Scope

The scope of the bounty program includes the following, subject to the exclusion below:

* ChainGPT AI Model & Chatbot (\* Incorrect answers given by the chatbot do not count toward the bounty)
* ChainGPT AI-Based Tools & Utilities
* DevAssist Browser Extension
* ChainGPT Blockchain (Layer 1 & Layer 2)
* ChainGPT Blockchain Ecosystem (web wallet, wallet extension, explorer, Wormhole, DEX)
* ChainGPT Documentation: <https://github.com/ChainGPT-org/docs>

**Excluded repository: chaingpt-claude-skill**

The chaingpt-claude-skill repository is excluded from the bug bounty program. Reports concerning vulnerabilities in that repository are not eligible for bounty payments. This exclusion is limited to that repository and does not extend to unrelated ChainGPT repositories or products.

This exclusion applies to reports submitted after its publication on the Bug Bounty Program page at <https://docs.chaingpt.org/bug-bounty>. It does not determine the treatment of reports submitted before publication.

Security issues concerning the excluded repository may still be reported through the channels below for technical review. Reviewing or fixing an issue does not, by itself, make the report eligible for a bounty.

#### Classification

**Critical Bugs**

Critical bugs can cause loss of funds or network downtime. These may include vulnerabilities in the deployed and supported versions of the blockchain client, smart contracts, or other software outlined in the Scope section.

**Non-Critical Bugs**

Non-critical bugs do not cause financial loss or harm to the network's availability. However, these may impact the experience of developers or users and have a workaround.

**Reward Assessment**

Each submission is assessed independently and is subject to verification and reclassification by the ChainGPT team. Approved rewards are paid in stablecoins, not CGPT tokens.

Awards of up to USD 5,000 may be considered for exceptional, financially impactful vulnerabilities in live, in-scope smart contracts, such as a vulnerability that could enable unauthorized withdrawal of funds. USD 5,000 is the maximum potential award, not a standard payment for every Critical bug. Other eligible reports are assessed individually, and no minimum reward is promised.

Whether to award a reward, and the amount of any reward, remain at ChainGPT's sole discretion under the Terms and Conditions below. Submitting a report, having it accepted for review, or receiving a severity classification does not automatically entitle the submitter to payment.

CertiK project information: <https://skynet.certik.com/projects/chaingpt>.

#### How to Report

To report a bug, please follow these steps:

1. Describe the issue clearly, referencing the affected source code where available and stating whether you believe the bug is Critical or Non-critical.
2. Attach the relevant information needed to reproduce the bug in a test environment.
3. Include the version information for the faulty software component and any other relevant system information (e.g., OS version).
4. Provide suggested solutions or mitigations, if known.
5. Submit your report through the Help Center at <https://help.chaingpt.org/> or by email to <support@chaingpt.org>. Start your message with "Critical" or "Non-critical", followed by a brief title of the bug, and include all relevant information in the submission. The ChainGPT team will determine the final classification after reviewing the report.

The ChainGPT team will review your report and classification and respond within two business days to see if the bug qualifies for the bounty program or if you'd like more information. Updates on the bug fix will be posted on our Discord server and Telegram channel. For non-critical bugs, the ChainGPT team will create an issue or pull request that you can track. For critical bugs that could result in funds loss, the fix will be shared after the code has been patched to prevent exploitation.

#### Terms and Conditions

* Each submission is assessed independently based on ChainGPT's findings, including the verified severity and impact of the reported issue. ChainGPT retains sole discretion to determine whether a report qualifies for a bounty, whether to award a reward, and the amount of any reward, subject to verification, applicable law and these program terms. Submission, acknowledgement, acceptance for review, verification, severity classification or remediation of a reported issue does not, by itself, create an entitlement to payment. ChainGPT may decide not to award a reward.
* Decisions on reward eligibility, whether to award a reward, and the reward amount are final for purposes of the program and are not subject to negotiation. ChainGPT is not obliged to enter into discussions or negotiations regarding those decisions, but may correct assessment errors or consider material new information at its discretion.
* We will respond to all submissions as soon as possible and pay approved rewards as quickly as possible, but we cannot promise processing time for claims.
* Participants warrant that they can legally receive bounties and that the work submitted is their original work. Additionally, participants must reside in a territory that allows payment of such rewards.
* Participants must be willing to undergo necessary KYC or AML checks.
* This program is not open to current or former employees or contractors of ChainGPT.
* ChainGPT reserves the right to alter or discontinue the Bounty Program without notice.
* Approved rewards will be paid in stablecoins, not CGPT tokens. Amounts stated in USD refer to United States dollars.
* Only reports submitted through the Help Center at <https://help.chaingpt.org/> or by email to <support@chaingpt.org> will be considered under this program, subject to its scope and exclusions. Please do not send bounty submissions by direct message to team members. Direct messages are not an accepted bounty submission channel.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chaingpt.org/bug-bounty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
