Quantum Audit Logo
Launch App

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

Is OpenGradient Safe?

OPGBase
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
Chart
Medium RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical8/10Governance2/10Upgrades6/10Checks passed3 of 5Findings1 Low · 2 Info3
SummaryAI Copilot

The OpenGradientToken contract is a standard ERC20 token with a fixed supply, built upon battle-tested OpenZeppelin libraries.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Top-10 concentration > 30%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 56.2%
  • LP top3 unlocked holders = 100.0%
  • 1 Low finding(s) from audit
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Top-10 concentration > 30% (94.1% total → 44.0% effective; 10.6% in EOAs, 83.5% in contracts — moderate)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 56.2% (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 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 43 of 5 checks passed
Contract verifiedVerified
OwnershipUnknown
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
83.5%Contracts10.6%Wallets5.9%Everyone else
83.5%Contracts10.6%5.9%
ContractsWalletsEveryone elseBubble area = share of supply
94.1%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking83.5%
  • Walletsanonymous holders, free to sell10.6%
  • Everyone elsethe rest of the supply5.9%
Effective concentrationwhat the score reads44.0%
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$401.7K across 3 pairs

The risk score reads depth across every pair.

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$381.9KShare of depth95.1%
Top-1 Unlocked Holder56.2%
Top-3 Unlocked100.0%
Unlocked LP held by
0xb68c…e8900x4a4c…9cc70x1bf0…d424

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

Security Findings

1 Low2 Info
Low

Irreversible Burn Function

The contract includes a burn function that allows any token holder to permanently destroy their own tokens. While this function is correctly implemented using OpenZeppelin's _burn and adheres to ERC20 standards, the action is irreversible. If a user accidentally burns tokens, there is no mechanism to recover them.L-01

Issue

The contract includes a burn function that allows any token holder to permanently destroy their own tokens. While this function is correctly implemented using OpenZeppelin's _burn and adheres to ERC20 standards, the action is irreversible. If a user accidentally burns tokens, there is no mechanism to recover them.

Fix

Educate users about the irreversible nature of the burn function. Implement clear UI/UX warnings in any front-end interfaces that interact with this function to prevent accidental token loss. Consider adding a multi-step confirmation process for burning tokens.

Status

Unresolved

Info

Immutability and Lack of Upgradeability

The OpenGradientToken contract is designed to be immutable and non-upgradeable. This design choice eliminates risks associated with proxy patterns and malicious upgrades, providing certainty about the contract's behavior over time (7.7 Upgrades). However, it also means that no bug fixes, feature enhancements, or adjustments can be made to the contract logic post-deployment. Any future changes would require deploying a new token contract and migrating users.I-01

Issue

The OpenGradientToken contract is designed to be immutable and non-upgradeable. This design choice eliminates risks associated with proxy patterns and malicious upgrades, providing certainty about the contract's behavior over time (7.7 Upgrades). However, it also means that no bug fixes, feature enhancements, or adjustments can be made to the contract logic post-deployment. Any future changes would require deploying a new token contract and migrating users.

Fix

Acknowledge this design choice and its implications. Ensure all initial requirements are thoroughly met, as no on-chain modifications are possible. Communicate clearly to the community that the token contract is immutable.

Status

Unresolved

Info

Fixed Supply and Absence of Administrative Control

The contract is designed with a fixed total supply of 1 billion tokens, all minted to a recipient during deployment, and explicitly states 'No centralized admin functions - completely decentralized' (7.4 Economic, 7.5 Governance). This design choice ensures decentralization and prevents arbitrary supply manipulation or centralized control. However, it also means there are no on-chain mechanisms for future tokenomics adjustments (e.g., adding staking rewards, adjusting supply for ecosystem growth) or emergency actions (e.g., pausing transfers in case of a critical vulnerability in an integrated protocol).I-02

Issue

The contract is designed with a fixed total supply of 1 billion tokens, all minted to a recipient during deployment, and explicitly states 'No centralized admin functions - completely decentralized' (7.4 Economic, 7.5 Governance). This design choice ensures decentralization and prevents arbitrary supply manipulation or centralized control. However, it also means there are no on-chain mechanisms for future tokenomics adjustments (e.g., adding staking rewards, adjusting supply for ecosystem growth) or emergency actions (e.g., pausing transfers in case of a critical vulnerability in an integrated protocol).

Fix

Ensure that the project's long-term vision and tokenomics are fully compatible with a fixed supply and lack of administrative control. If future flexibility is desired, consider off-chain governance mechanisms or separate contracts for ecosystem incentives that interact with this token.

Status

Unresolved

Analysis

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

The OpenGradientToken contract is a standard ERC20 token with a fixed supply, built upon battle-tested OpenZeppelin libraries. It explicitly lacks administrative functions and is immutable, ensuring a high degree of decentralization and predictability. The custom burn function is correctly implemented. The audit identified no critical or high-severity vulnerabilities. Informational findings relate to the inherent trade-offs of its immutable and decentralized design.

Technical8/10Low risk

The contract leverages battle-tested OpenZeppelin ERC20 and ERC20Permit implementations, ensuring robust and standard token functionality (7.2 Code Security). Solidity 0.8.26 provides default overflow/underflow checks, and OpenZeppelin's internal _update function uses unchecked blocks judiciously where safety is guaranteed, mitigating arithmetic risks. The custom burn function is a straightforward wrapper around _burn, maintaining security standards. No significant technical vulnerabilities were identified in the custom logic.

Governance2/10High risk

The contract is designed for complete decentralization, with a fixed total supply of 1 billion tokens minted at deployment (7.4 Economic, 7.5 Governance). There are no administrative functions, owner privileges, or upgradeability, which eliminates risks associated with centralized control and potential governance attacks. This design ensures predictable tokenomics and prevents arbitrary supply changes. The immutable nature and lack of administrative control mean no on-chain mechanisms exist for future tokenomics adjustments or emergency interventions, which could limit long-term adaptability.

Upgrades6/10Medium risk

The OpenGradientToken contract is explicitly designed as an immutable, non-upgradeable token, eliminating all risks associated with proxy patterns, upgradeability bugs, or malicious upgrade paths (7.7 Upgrades). This provides certainty regarding the contract's code and behavior over its lifetime. The immutability means that no bug fixes, feature enhancements, or adjustments can be made to the contract logic post-deployment, requiring a new deployment and migration if changes are ever needed.

Final RecommendationWhat to do about this score

The OpenGradientToken contract is robust and secure due to its simplicity and reliance on OpenZeppelin's audited libraries.

Users should be aware of the token's immutable nature and the absence of administrative control, which means no future changes or emergency interventions are possible. Projects integrating with this token should account for its fixed supply and decentralized design in their long-term planning.

Contract & Record

1 audit on record
TypeOpenGradientToken
NetworkBase
Token age2mo
Contract0xfbc2…f5eb
Deployer0x4905…d2dc
Badge for your website
OpenGradient 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 4, 202637Medium
  2. Jul 23, 202636Medium

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

Related Audits

6 more on the recordAll audits
ZoraBase37MediumnoiceBase37MediumChainLink TokenLINK · Base37Mediumthe sleeping giantTSG · Base37MediumMUSWORLDMUSEWORLD · Base37MediumAave TokenAAVE · Base38Medium

Would You Like a More Detailed Audit of OpenGradient?

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