Quantum Audit Logo
Launch App

On-chain security analysis — is it a scam or legit?

Is ChainGPT Safe?

CGPTBNB Chain
Not verified This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →
Last checked Sep 4, 2026 · 1 audit on record
SummaryAI Copilot

The ChainGPT token contract is a standard ERC20 implementation, inheriting from battle-tested OpenZeppelin libraries for core functionalities, burn capabilities, and ownership management.

Read the full analysis
What raised the score
  • Top-10 concentration > 30%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 99.9%
  • LP top3 unlocked holders = 100.0%
  • 1 High finding(s) from audit
  • 1 Medium finding(s) from audit
  • 1 Low finding(s) from audit
Exact factors
  • Top-10 concentration > 30% (59.0% total → 41.9% effective; 30.4% in EOAs, 28.6% in contracts — moderate)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 99.9% (independent LP — depth risk, pool = 95% of DEX liquidity)
  • LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 95% of DEX liquidity)
  • 1 High finding(s) from audit
  • 1 Medium finding(s) from audit
  • 1 Low finding(s) from audit

Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed

Security Checklist

as of audit · Sep 46 of 7 checks passed
Contract verifiedVerified
OwnershipRenounced
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code
HoneypotNone found
Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026
28.6%Contracts30.4%Wallets41.0%Everyone else
28.6%Contracts30.4%Wallets41.0%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
59.0%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking28.6%
  • Walletsanonymous holders, free to sell30.4%
  • Everyone elsethe rest of the supply41.0%
Effective concentrationwhat the score reads41.9%
How holder types affect the score

Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.

Holder balances as recorded by the audit of Sep 4, 2026

Liquidity

as of audit · Sep 4$981.1K across 17 pairs
LP tokensNot locked

The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.

Analysed pool$935.9KShare of depth95.4%
Top-1 Unlocked Holder99.9%
Top-3 Unlocked100.0%
Unlocked LP held by
0x5930…9fbe0x556b…d59e0x966d…e41a0x2951…29b10x8325…100f0x5f0f…29090xe505…9ae4

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

Security Findings

1 High1 Medium1 Low1 Info
High

Centralized Initial Token Distribution

The ChainGPT contract's constructor mints the entire initial token supply (1,000,000,000 tokens) directly to msg.sender (the contract deployer). This design choice results in a highly centralized initial distribution, where a single address holds 100% of the circulating supply. This centralization introduces significant economic risk, as the deployer has complete control over the initial market dynamics and distribution. A compromise of this single address could have a catastrophic impact on the token's ecosystem.H-01

Issue

The ChainGPT contract's constructor mints the entire initial token supply (1,000,000,000 tokens) directly to msg.sender (the contract deployer). This design choice results in a highly centralized initial distribution, where a single address holds 100% of the circulating supply. This centralization introduces significant economic risk, as the deployer has complete control over the initial market dynamics and distribution. A compromise of this single address could have a catastrophic impact on the token's ecosystem.

Fix

While this is a common design for new tokens, it's crucial to acknowledge the associated risks. Implement a clear, transparent plan for token distribution to mitigate the risks of centralization. Consider using a vesting schedule, multi-signature wallets, or a timelock for large portions of the supply to reduce immediate control by a single entity.

Status

Unresolved

Medium

Lack of Emergency Pause Mechanism

The ChainGPT token contract does not include a Pausable mechanism. In the event of a critical vulnerability discovery, a major market exploit, or other unforeseen circumstances, the contract owner would not have the ability to temporarily halt token transfers or other critical functions. This absence could lead to unmitigated losses or allow an exploit to propagate without immediate intervention, impacting the protocol's ability to respond to emergencies (7.8 Operations).M-01

Issue

The ChainGPT token contract does not include a Pausable mechanism. In the event of a critical vulnerability discovery, a major market exploit, or other unforeseen circumstances, the contract owner would not have the ability to temporarily halt token transfers or other critical functions. This absence could lead to unmitigated losses or allow an exploit to propagate without immediate intervention, impacting the protocol's ability to respond to emergencies (7.8 Operations).

Fix

Integrate OpenZeppelin's Pausable contract or implement a similar mechanism that allows the owner (or a designated multi-signature wallet) to pause and unpause critical functions like transfer, transferFrom, approve, mint, and burn. This provides a crucial emergency stop-gap measure.

Status

Unresolved

Low

No Recovery for Accidentally Sent Assets

The contract lacks functions to recover accidentally sent ERC20 tokens or native currency (e.g., BNB on BSC) that might be sent directly to the contract address. If users or other contracts mistakenly transfer assets to the ChainGPT contract, these assets will become permanently locked and irrecoverable, leading to a loss for the sender.L-01

Issue

The contract lacks functions to recover accidentally sent ERC20 tokens or native currency (e.g., BNB on BSC) that might be sent directly to the contract address. If users or other contracts mistakenly transfer assets to the ChainGPT contract, these assets will become permanently locked and irrecoverable, leading to a loss for the sender.

Fix

Implement a function, callable only by the contract owner, to recover arbitrary ERC20 tokens and native currency accidentally sent to the contract. This function should include checks to prevent the owner from withdrawing the contract's own CGPT tokens.

Status

Unresolved

Info

Owner Privileges and Single Point of Control

The contract utilizes the Ownable pattern, granting a single address (the owner) exclusive control over administrative functions such as transferOwnership and renounceOwnership. While this provides a clear administrative structure, it introduces a single point of failure. If the owner's private key is compromised, or if the owner acts maliciously, the integrity of these administrative controls could be jeopardized (7.3 Access Control).I-01

Issue

The contract utilizes the Ownable pattern, granting a single address (the owner) exclusive control over administrative functions such as transferOwnership and renounceOwnership. While this provides a clear administrative structure, it introduces a single point of failure. If the owner's private key is compromised, or if the owner acts maliciously, the integrity of these administrative controls could be jeopardized (7.3 Access Control).

Fix

For enhanced security and decentralization, consider transferring ownership to a multi-signature wallet (e.g., Gnosis Safe) or a time-locked contract. This distributes control and adds a layer of protection against a single point of failure or malicious intent.

Status

Unresolved

Analysis

AI Copilotas of audit · Sep 4
Executive SummaryWhat the contract is and what the review found

The ChainGPT token contract is a standard ERC20 implementation, inheriting from battle-tested OpenZeppelin libraries for core functionalities, burn capabilities, and ownership management. The contract mints a fixed total supply to the deployer upon creation. Key findings include a highly centralized initial token distribution and the absence of an emergency pause mechanism, which are common considerations for token contracts.

Technical9/10Low risk

The ChainGPT token contract leverages battle-tested OpenZeppelin libraries for its ERC20, Ownable, and ERC20Burnable functionalities, ensuring a high standard of code security (7.2 Code Security). Arithmetic operations are protected against overflow/underflow by Solidity 0.8.0+ default checks or explicit require statements before unchecked blocks. Access control (7.3 Access Control) is managed via the Ownable pattern, restricting administrative functions like transferOwnership to the designated owner. A notable technical risk is the absence of a pause mechanism, which could limit emergency response capabilities.

Governance5/10Medium risk

The economic model (7.4 Economic) of the ChainGPT token is characterized by a fixed total supply, with the entire initial supply minted to the deployer, creating a highly centralized distribution at launch (7.1 Architecture). This centralization extends to governance (7.5 Governance) through the Ownable pattern, where a single address controls administrative functions, including the ability to transfer ownership. While this provides clear administrative control, it introduces a single point of failure if the owner's key is compromised or misused.

Upgrades9/10Low risk

The ChainGPT contract is implemented as a standard, non-upgradeable contract (7.7 Upgrades). This design choice eliminates the complexities and potential risks associated with proxy patterns and upgrade mechanisms, such as storage collisions or logic errors during upgrades. However, it also means that any discovered vulnerabilities or desired feature enhancements would require a new contract deployment and a token migration process.

Final RecommendationWhat to do about this score

It is recommended to implement a Pausable mechanism to allow for emergency halts of critical token functions in unforeseen circumstances, enhancing the contract's resilience against potential exploits or market instability.

Additionally, consider adding a recovery function for accidentally sent ERC20 tokens or native currency to prevent permanent loss of assets due to user error. For long-term decentralization, explore strategies for distributing ownership and control over administrative functions, such as multi-signature wallets or a decentralized autonomous organization (DAO).

Contract & Record

1 audit on record
TypeToken
NetworkBNB Chain
Token age2y
Contract0x9840…0f98
Deployer0xd9b4…6cb3
Badge for your website
ChainGPT security record badge

Free for any token on the record. It links to this page and always shows the current score and the date it was checked.

Audit History
  1. Sep 2, 202623Low

Score changes are recorded as dated snapshots — history is append-only and cannot be edited.

Would You Like a More Detailed Audit of ChainGPT?

Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.

Get Detailed Audit Is this your token? Publish your own audit on this page