Quantum Audit Logo
Launch App

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

Is VEIL Token Safe?

VEILBase
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
Low RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical10/10Governance6/10Upgrades9/10Checks passed4 of 5Findings3 Info3
SummaryAI Copilot

This audit report is based on the provided OpenZeppelin Ownable and ERC20 library code, as the specific VEILToken contract implementation was not provided.

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 = 52.5%
  • LP top3 unlocked holders = 95.0%
Exact factors
  • Top-10 concentration > 30% (64.6% total → 43.1% effective; 28.8% in EOAs, 35.9% in contracts — moderate)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 52.5% (independent LP — depth risk, pool = 97% of DEX liquidity)
  • LP top3 unlocked holders = 95.0% (independent LP — depth risk, pool = 97% of DEX liquidity)

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 44 of 5 checks passed
Contract verifiedVerified
OwnershipRenounced
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
35.9%Contracts28.8%Wallets35.4%Everyone else
35.9%Contracts28.8%Wallets35.4%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
64.6%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking35.9%
  • Walletsanonymous holders, free to sell28.8%
  • Everyone elsethe rest of the supply35.4%
Effective concentrationwhat the score reads43.1%
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$538.6K across 8 pairs
Show 2 more 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$525.1KShare of depth97.5%
Top-1 Unlocked Holder52.5%
Top-3 Unlocked95.0%
Unlocked LP held by
0x9a88…bd090x75c6…56eb0x3112…a58e0xd248…0e490x391d…0f64

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

Security Findings

3 Info
Info

Renounced Ownership Implications

The Ownable contract's ownership has been renounced, as indicated by ownership_renounced: true. This means the owner() address is address(0), and any functions protected by the onlyOwner modifier are permanently inaccessible. This design choice enhances decentralization by removing a single point of control.I-01

Issue

The Ownable contract's ownership has been renounced, as indicated by ownership_renounced: true. This means the owner() address is address(0), and any functions protected by the onlyOwner modifier are permanently inaccessible. This design choice enhances decentralization by removing a single point of control.

Fix

Acknowledge that renounced ownership means no administrative functions (e.g., transferOwnership, renounceOwnership itself, or any onlyOwner functions in the inheriting VEILToken contract like _mint or _burn if exposed) can ever be executed. This is a permanent state and should be clearly communicated to users and stakeholders.

Status

Unresolved

Info

Reliance on Standard OpenZeppelin Libraries

The contract utilizes well-audited and widely adopted OpenZeppelin libraries for its ERC20 and Ownable functionalities. This significantly reduces the likelihood of common vulnerabilities and contributes to high code security and reliability.I-02

Issue

The contract utilizes well-audited and widely adopted OpenZeppelin libraries for its ERC20 and Ownable functionalities. This significantly reduces the likelihood of common vulnerabilities and contributes to high code security and reliability.

Fix

Continue to leverage established and audited libraries. Ensure that any custom logic added in the VEILToken contract (not provided for audit) maintains the same high security standards and does not introduce new vulnerabilities.

Status

Unresolved

Info

Absence of Emergency Pause Mechanism

The contract does not include a mechanism to pause transfers or other critical operations in case of an emergency, such as a major exploit or vulnerability discovery. While common for simple tokens, this means no immediate response is possible for certain attack vectors.I-03

Issue

The contract does not include a mechanism to pause transfers or other critical operations in case of an emergency, such as a major exploit or vulnerability discovery. While common for simple tokens, this means no immediate response is possible for certain attack vectors.

Fix

Consider if an emergency pause mechanism (e.g., using OpenZeppelin's Pausable contract) is necessary for the project's risk profile. If implemented, ensure the pause functionality is controlled by a secure, multi-signature wallet or a robust governance process, especially given the renounced ownership of the Ownable component.

Status

Unresolved

Analysis

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

This audit report is based on the provided OpenZeppelin Ownable and ERC20 library code, as the specific VEILToken contract implementation was not provided. The analysis assumes VEILToken inherits from these standard components. The contract benefits from using well-audited OpenZeppelin libraries. A key operational characteristic is that ownership has been renounced, which removes centralized control but also administrative flexibility.

Technical10/10Low risk

The technical architecture (7.1) is robust, leveraging standard and well-audited OpenZeppelin ERC20 and Ownable contracts. Code security (7.2) is high, with appropriate use of unchecked blocks for gas optimization where safety is guaranteed by prior checks. Access control (7.3) is managed by the Ownable pattern, which, given renounced ownership, means no single entity can exert administrative control. External interactions (7.6) are limited to standard ERC20 interfaces, reducing attack surface. Operations (7.8) are straightforward, though administrative functions are disabled due to renounced ownership.

Governance6/10Medium risk

The economic model (7.4) is a standard ERC20 token, with no complex mechanisms identified in the provided library code. Governance (7.5) is effectively decentralized due to the renounced ownership, meaning no single address can control token parameters or administrative functions like _mint or _burn if they were exposed by the inheriting contract and protected by onlyOwner. This eliminates risks associated with a malicious or compromised owner, but also removes any potential for administrative intervention or upgrades.

Upgrades9/10Low risk

The provided contracts are not designed for upgradeability (7.7), as indicated by the absence of proxy patterns (e.g., UUPS, Transparent) or Initializable contracts. This means the contract's logic is immutable once deployed, eliminating upgrade-related risks but also precluding future modifications or bug fixes to the core logic.

Final RecommendationWhat to do about this score

Given the renounced ownership, it is crucial for users and integrators to understand that the token contract is immutable and lacks any administrative control.

Ensure that the initial token supply and distribution are correctly configured, as no further minting or burning can be performed by an owner. Consider the implications of the absence of an emergency pause mechanism for potential future scenarios.

Contract & Record

1 audit on record
TypeVEILToken
NetworkBase
Token age1y
Contract0x767a…7d7f
Deployer0x19f4…3702
Badge for your website
VEIL Token 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, 20267Low
  2. Aug 12, 20269Low

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

Related Audits

6 more on the recordAll audits
Briun ArmstrungBRIUN · Base8LowBasedPepePEPE · Base8LowToshiBase5LowCoinye WestCOINYE · Base9LowBASEPADBase9LowDebtReliefBotDRB · Base10Low

Would You Like a More Detailed Audit of VEIL Token?

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