Skip to main content

ChainGPT

ChainGPT — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

ChainGPT — an AI/Other | Infra project: a set of AI tools for Web3 (chatbot, smart contract generation/audit, API/SDK). Token: CGPT (native BEP‑20 on BNB Smart Chain; there is also a bridged ERC‑20 on Ethereum and a bridge version on Solana).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a set of applications and APIs for “crypto assistant” tasks (chat, summaries/explanations, smart contract code generation/audit, etc.).
  • Who it’s for: crypto users (research/hints), teams and developers (integration via API/SDK).
  • Why onchain/token: the CGPT token is used as the unit of account/access to the ecosystem (credits for requests, staking tiers, DAO voting); the core logic of the product is mostly offchain.
  • What you can actually touch (Tier‑1): the Web3 AI Chatbot https://app.chaingpt.org/web3-chatbot and the QuickStart Guide (API/SDK) https://docs.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/web3-ai-chatbot-and-llm-api-and-sdk/javascript/quickstart-guide.

How it works (very briefly)

  1. The user does: asks a question in the chatbot or calls the API/SDK (chat/tools).
  2. The system does: processes the request with an LLM service and returns a response/result (offchain).
  3. The user gets: a response, a summary/analysis or a tool result (for example, smart contract generation/audit).
  4. Where the blockchain is: onchain is represented by the CGPT token (and the related staking/entitlement accounting modules); inference/processing is offchain.
  5. Token role: CGPT is used for payment/conversion into credits (CGPTc), staking for tier benefits/participation in the launchpad, and for governance (DAO).

Quick links: AI thesis fit

Project passport

Field Value
Project name ChainGPT
Also known as (aliases) ChainGPT; Chain-GPT; CGPT
Logo (logo) ../assets/75_chaingpt_logo.svg
Token symbol (ticker) CGPT
Category AI/Other | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2023
Project status (status) active
Token (standard) BEP-20
Token contract 0x9840652DC04fb9db2C43853633f0F62BE6f00f98
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) CGPT ↔ CGPTc usage credits; staking → CGPTsp/tiers/CGPTvp; part of the fees is burned
Governance DAO
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) Web3 AI tools (chatbot + smart-contract generation/audit)
Use‑case (use_case) AI assistant + dev API for Web3
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

ChainGPT positions itself as “AI infrastructure for Web3” and is a set of applications (chatbot/tools) and developer interfaces (API/SDK) that help solve typical tasks of crypto users and teams: quick research, summaries and explanations, Solidity code generation/audit, monitoring, etc.

Important: in its current form this is mostly an offchain product (an LLM service and web applications). The onchain part that could be confirmed per Tier‑1 sources is the CGPT token (native BEP‑20 on BNB Smart Chain and bridged representations on other networks) and the mechanics related to it (staking points/voting, tier access).

Features/modules

  • Web3 AI Chatbot: a chatbot for Web3/crypto (web/Telegram/Discord).
  • AI tools: a smart contract generator and auditor, AI news/alerts, an NFT generator, etc. (within the suite).
  • Dev integration: REST API + SDK (example: the QuickStart for Web3 AI Chatbot & LLM).
  • Ecosystem modules: staking/tiers (CGPTsp/CGPTvp) and DAO governance.

Typical scenarios

  • Scenario 1 (user): asks the chatbot a question about a protocol/term/news item → gets a summary/explanation/hints.
  • Scenario 2 (developer): integrates the chat/LLM via the API/SDK → adds an AI assistant inside their dApp/website.
  • Scenario 3 (token holder): stakes CGPT → gets tier benefits, votes in the DAO, improves access/terms in the ecosystem.

Getting started (wallet/network)

  • What you need: web access to the products; for the API — an API key; for onchain actions — an EVM wallet.
  • Network/chain: for the token/staking, the documentation lists native CGPT on BNB Smart Chain (as well as bridge versions on Ethereum/Solana).
  • Fees: offchain — CGPTc/credits are deducted for requests; onchain — network fees for transfers/staking on the chosen network.

Architecture/tech (non‑AI)

  • Components: web applications (AI Hub), REST API, SDK; onchain — the CGPT token contracts (native/bridge) and the infrastructure related to them.
  • Participant roles: users/developers (use the web/API), token holders (transfers/staking), DAO participants (proposals/voting).
  • Where logic runs: inference/request processing — offchain; token ownership accounting and token operations — onchain on the respective networks.
  • Dependencies: EVM infrastructure (BNB Smart Chain/Ethereum), bridges for the bridged versions of the token (ChainPort/Stargate are mentioned in the documentation).

Token/economics (expanded, no forecasts)

  • Token utility: in the documentation, CGPT is described as the utility+governance token of the ecosystem; pay‑per‑use for the AI tools is implemented via CGPTc credits (converted from CGPT), as well as via staking privileges/tiers.
  • Who pays fees: users (for requests/tools via CGPTc) and ecosystem participants (onchain network fees for transactions).
  • Where fees go/what happens to them: the documentation describes a burn mechanism for part of the commercial transactions/features (vector “touchpoints”).
  • Issuance/burn: the supply in the documentation is listed as 1B; the burn mechanism is described separately for BSC.
  • Incentive mechanisms: CGPT staking (CGPTsp) affects tier access and voting power (CGPTvp).
  • Distribution/vesting: tokenomics tables are published (rounds, shares, cliff/vesting).
  • Treasury: the DAO documentation lists a fund/treasury (9% of supply) and an unlock schedule (cliff + monthly vesting).

Governance

  • Who makes decisions: DAO (ChainGPT DAO).
  • How it works: the documentation describes membership via ownership+staking of CGPT, a snapshot of voting power at the moment a proposal is created, and on‑chain deployment of the proposal.
  • Where: the DAO interface is listed in the documentation; details of the CGPTvp/CGPTsp metrics — in the token section.
  • Keys/multisig: public parameters of the contract management keys are not confirmed per Tier‑1 → —.

Security and incidents

  • Audits: the token documentation provides links to Certik/Hacken; the token repository also lists an audit link (see Evidence).
  • Bug bounty: the bug bounty program is described in the documentation (see Evidence).
  • Incidents: no public postmortems/incidents were found per Tier‑1 → —.
  • Threat model (simplified): the key risks are the centralized component of the offchain service (quality/availability/policies), bridge risks for the bridged versions of the token, and the standard risks of token contracts/staking.

Project status and timeline

  • Current status: the products and the token are active; the documentation lists a beta status for the chatbot.
  • Key milestones: the token launch and the development of the suite of tools (details — in the documentation/roadmap).
  • Roadmap: published in the documentation (the Road Map section; separate pages by quarter).

Ecosystem/integrations

  • Integrations: the chatbot is available in web/Telegram/Discord; there is a REST API + SDK for integrations; the token documentation mentions bridges for the bridged versions.
  • Partners: not separately verified per Tier‑1 → —.
  • Where it is used: the main “touchpoint” is the web application and developer integrations via the API/SDK.

AI component of the project

  • What is real AI here? AI tools/a chatbot for Web3 and a developer API/SDK (an LLM service), described in the official documentation.
  • What is truly onchain? The CGPT token (native BEP‑20 on BNB Smart Chain) and the related ownership/staking/voting mechanics; AI request processing happens offchain.
  • Why is a token needed? Payment/conversion into credits for using the AI tools, staking tiers and participation in DAO governance.
  • Red flags (based on the information found): a future “AIVM blockchain” is claimed (intent), but deployed onchain components of this part are not confirmed per Tier‑1; most of the product is centralized (offchain).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Web3 AI Chatbot is a specialized chatbot for Web3/crypto with LLM functionality and scenarios (research/trading assistant, etc.).
  • Evidence: Tier‑1 — https://docs.chaingpt.org/ai-tools-and-applications/ai-web3-chatbot
  • Why sufficient / why not (one line): the product page describes the purpose and usage scenarios of the chatbot.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a live web demo (Chatbot) and a technical example of integration via REST/SDK (a QuickStart with endpoint/parameters).
  • Evidence: Tier‑1 — https://app.chaingpt.org/web3-chatbot ; https://docs.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/web3-ai-chatbot-and-llm-api-and-sdk/javascript/quickstart-guide
  • Why sufficient / why not (one line): there is a reproducible path to “log in and try” and “call the API”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — — (no published quality metrics/benchmarks were found per Tier‑1)
  • Why sufficient / why not (one line): without published metrics/testing protocols the component cannot be credited.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): dev docs on using the Web3 AI Chatbot & LLM via the REST API and the JavaScript SDK are published.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/web3-ai-chatbot-and-llm-api-and-sdk/javascript/quickstart-guide
  • Why sufficient / why not (one line): the presence of parameters/endpoint/integration examples meets the “technical description” requirement.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain (native CGPT); a bridge CGPT on Ethereum is also listed.
  • Addresses/identifiers: BSC 0x9840652DC04fb9db2C43853633f0F62BE6f00f98; Ethereum 0x25931894a86d47441213199621f1f2994e1c39aa.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token ; https://bscscan.com/address/0x9840652DC04fb9db2C43853633f0F62BE6f00f98 ; https://etherscan.io/token/0x25931894a86d47441213199621f1f2994e1c39aa
  • Why sufficient / why not (one line): the token addresses and networks are listed in the official documentation and confirmed by the explorers.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: per Tier‑1, no addresses/contracts are confirmed that prove critical onchain logic beyond the token (for example, protocol contracts of the service).
  • Evidence: Tier‑1 — — (apart from the token and general descriptions of the DAO/tiers)
  • Why sufficient / why not (one line): without specific addresses/contracts/calls we do not credit it.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: inference/tools work offchain; no evidence was found per Tier‑1 that the key value “breaks down” without onchain.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/ai-tools-and-applications/ai-web3-chatbot
  • Why sufficient / why not (one line): the product is described as an AI suite/chatbot; the onchain part is not shown as critical for performing the core functions.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, CGPT.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token
  • Why sufficient / why not (one line): the documentation explicitly records the token and its specifications.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): pay‑per‑use for the AI tools is implemented via CGPTc (credits), which are acquired by converting CGPT.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token
  • Why sufficient / why not (one line): the documentation describes the cost of requests in CGPTc and the CGPT → CGPTc link.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): staking CGPT yields CGPTsp (staking points), which affect tiers/access and opportunities (including launchpad benefits).
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token ; https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/cgptsp-staking-points ; https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/tier-system-and-benefits
  • Why sufficient / why not (one line): there is a formula for accruing CGPTsp and a link to tiers/access.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance in the DAO is tied to stake/voting power (CGPTvp), and membership is linked to ownership and staking of CGPT.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/dao-governance ; https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/cgptvp-voting-power
  • Why sufficient / why not (one line): the documentation describes the DAO process and the voting power metric tied to staking.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): a significant part of the product is an offchain service, and staking is explicitly listed as optional; the payment model could be implemented differently (subscription/fiat), so the “irreplaceability” of the token is not proven.
  • Evidence: Tier‑1 — https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token
  • Why sufficient / why not (one line): the documentation states that staking is optional and not required to use the products; without onchain criticality we consider the token replaceable.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.chaingpt.org/ A description of the ecosystem of AI tools and the claimed future AIVM initiative (AI intent).
Tier‑1 https://docs.chaingpt.org/ai-tools-and-applications/ai-web3-chatbot What exactly the Web3 AI Chatbot does and where it is available (web/Telegram/Discord).
Tier‑1 https://docs.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/web3-ai-chatbot-and-llm-api-and-sdk/javascript/quickstart-guide A reproducible QuickStart for REST/SDK (endpoint/parameters/example).
Tier‑1 https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token Specifications/utility of the CGPT token, addresses (BSC/Ethereum/Solana), pay‑per‑use (CGPTc), staking/gov.
Tier‑1 https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/tokenomics Tokenomics tables: distribution, cliff/vesting, the DAO share, etc.
Tier‑1 https://docs.chaingpt.org/our-ecosystem/dao-governance DAO mechanics: membership via CGPT, treasury 9% of supply, snapshots and the voting process.
Tier‑1 https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/cgptsp-staking-points What CGPTsp is and how staking points are accrued.
Tier‑1 https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/cgptvp-voting-power What CGPTvp (voting power) is and its link to CGPTsp.
Tier‑1 https://docs.chaingpt.org/our-ecosystem/cgpt-utility-token/burn-mechanism A description of the burn mechanism and the burn “touchpoints” for CGPT.
Tier‑1 https://docs.chaingpt.org/bug-bounty The existence of a bug bounty and the scope/reporting process.
Tier‑1 https://bscscan.com/address/0x9840652DC04fb9db2C43853633f0F62BE6f00f98 Onchain confirmation of the native CGPT contract on BNB Smart Chain (BEP‑20).
Tier‑1 https://etherscan.io/token/0x25931894a86d47441213199621f1f2994e1c39aa Onchain confirmation of the bridge version of CGPT on Ethereum (ERC‑20).
Tier‑1 https://github.com/ChainGPT-org/CGPT_Token The token contract repository (description of supply=1B, utility, a link to the audit).

No comments to display

Back to top