CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
ChainGPT logo
ChainGPT
Infrastructure
NFT
AI
Max Payout
$5,000
Project Overview

ChainGPT is an advanced AI model purpose-built for blockchain and crypto-related applications. Leveraging cutting-edge algorithms and high-performance computing, ChainGPT provides fast, accurate solutions to complex problems in the Web3 space. Designed for individuals, developers, and enterprises alike, it offers a suite of powerful tools for research, development, and real-time insights—making it an essential resource for navigating the blockchain ecosystem.

Rewards by Severity

Program Overview ChainGPT runs a formal bug bounty program to ensure the ongoing security and reliability of its AI-powered blockchain ecosystem. By encouraging developers, ethical hackers, and security experts to responsibly disclose vulnerabilities, the program helps minimize risks to user funds and maintain high software integrity across core components, including smart contracts and blockchain infrastructure.

Reward Structure The program uses a 4-tier severity classification, with rewards based on the severity and impact of the issue reported. Critical bugs, which may result in fund loss or cause network downtime, are eligible for rewards up to 5,000 CGPT tokens, and must affect deployed and officially supported smart contracts or blockchain clients. Non-critical bugs, which do not impact fund security or availability but may affect user or developer experience, can earn up to 500 CGPT tokens. Final classification and reward amounts are subject to verification and adjustment by the ChainGPT team.

Submission Requirements All submissions must include a functional proof of concept (PoC) along with detailed reproduction steps. Reports without code or real-world impact demonstration will not be eligible for rewards.

Payouts Although reward tiers are defined in CGPT tokens, payouts are made in USDT, distributed by the ChainGPT team after successful report validation and completion of KYC.

Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://github.com/ChainGPT-org/
Smart Contract
CGPT TOKEN
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of any user funds - whether at-rest or in-motion - other than unclaimed yield
Major
Faulty usage of proxy patterns
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Users could lose funds due to rounding
Low
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Best practice critiques
Sybil attacks
Centralization risks
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks.
  • Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Any testing with mainnet or public testnet contracts, all testing should be done on private testnets.
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceApr 13, 2023
Last Updated3mo 22d ago
Funds Reserved$50,000
Max Payout$5,000
Skynet Score
93.03
AAA
KYC
Required
PoC
Required
View on Skynet