Quantum Audit Logo
Launch App

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

Is Highstreet token Safe?

HIGHEthereum
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/10Governance1/10Upgrades6/10Checks passed3 of 5Findings1 Low · 2 Info3
SummaryAI Copilot

The Highstreet Token (HIGH) contract is a standard ERC-20 implementation, inheriting from OpenZeppelin's battle-tested contracts.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Top-10 concentration > 50%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 79.6%
  • LP top3 unlocked holders = 91.0%
  • 1 Low finding(s) from audit
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Top-10 concentration > 50% (68.6% total → 59.0% effective; 52.6% in EOAs, 16.0% in contracts — heavy)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • LP top1 unlocked holder = 79.6% (independent LP — depth risk, pool = 99% of DEX liquidity)
  • LP top3 unlocked holders = 91.0% (independent LP — depth risk, pool = 99% 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
16.0%Contracts52.6%Wallets31.4%Everyone else
16.0%Contracts52.6%Wallets31.4%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
68.6%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking16.0%
  • Walletsanonymous holders, free to sell52.6%
  • Everyone elsethe rest of the supply31.4%
Effective concentrationwhat the score reads59.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$82.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$81.9KShare of depth99.0%
Top-1 Unlocked Holder79.6%
Top-3 Unlocked91.0%
Unlocked LP held by
0x94b5…84410xd163…d3dd0x4aeb…a04e0xe78b…6a110x459f…ec980x598b…02600x0a6d…b1480xd2c8…67c40x944b…a3110x1bd0…7273

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

Security Findings

1 Low2 Info
Low

Lack of Emergency Pause Functionality

The HIGH token contract, being a standard ERC-20, does not include a mechanism to pause transfers or other critical functions in case of an emergency (e.g., a critical vulnerability discovered in an integrated DeFi protocol, or a major market manipulation event). While not a direct vulnerability in the token contract itself, the absence of such a feature can limit the project's ability to react to unforeseen circumstances, potentially mitigating larger losses.L-01

Issue

The HIGH token contract, being a standard ERC-20, does not include a mechanism to pause transfers or other critical functions in case of an emergency (e.g., a critical vulnerability discovered in an integrated DeFi protocol, or a major market manipulation event). While not a direct vulnerability in the token contract itself, the absence of such a feature can limit the project's ability to react to unforeseen circumstances, potentially mitigating larger losses.

Fix

Consider implementing a pausable mechanism (e.g., using OpenZeppelin's Pausable module) to allow a trusted role (e.g., a multi-sig wallet) to temporarily halt token transfers. This should be used judiciously and only in extreme emergencies, with clear communication to the community.

Status

Unresolved

Info

Centralized Initial Token Distribution

The HIGH token's entire supply (100,000,000 * 1e18) is minted to a single minter address during contract deployment. This design choice results in a highly centralized initial distribution, where one address holds 100% of the token supply. While not a technical vulnerability, it implies significant control by the minter over the token's initial market dynamics and potential for large-scale movements.I-01

Issue

The HIGH token's entire supply (100,000,000 * 1e18) is minted to a single minter address during contract deployment. This design choice results in a highly centralized initial distribution, where one address holds 100% of the token supply. While not a technical vulnerability, it implies significant control by the minter over the token's initial market dynamics and potential for large-scale movements.

Fix

Ensure the minter address is a secure, multi-signature wallet controlled by trusted parties. Clearly communicate the distribution strategy and the role of the minter address to the community to manage expectations regarding centralization and potential market impact.

Status

Unresolved

Info

Immutability and Lack of Administrative Flexibility

The HIGH token contract is deployed as a standalone, non-upgradeable contract with no administrative functions beyond the standard ERC-20 interface. There are no owner-controlled mint, burn, setTax, or similar functions. This immutability ensures predictable behavior and reduces attack surface, but it also means the contract cannot be modified or enhanced post-deployment, nor can any administrative actions be taken (e.g., recovering accidentally sent tokens, adjusting parameters).I-02

Issue

The HIGH token contract is deployed as a standalone, non-upgradeable contract with no administrative functions beyond the standard ERC-20 interface. There are no owner-controlled mint, burn, setTax, or similar functions. This immutability ensures predictable behavior and reduces attack surface, but it also means the contract cannot be modified or enhanced post-deployment, nor can any administrative actions be taken (e.g., recovering accidentally sent tokens, adjusting parameters).

Fix

This is a fundamental design choice. If immutability is the desired goal, ensure all design decisions are final and thoroughly reviewed. If future flexibility or limited administrative control is ever anticipated, consider an upgradeable proxy pattern or adding specific, carefully scoped administrative functions (e.g., recoverERC20) controlled by a multi-signature wallet.

Status

Unresolved

Analysis

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

The Highstreet Token (HIGH) contract is a standard ERC-20 implementation, inheriting from OpenZeppelin's battle-tested contracts. Its custom logic is minimal, consisting solely of an initial mint of a fixed total supply to a specified minter address during construction. The contract exhibits high code quality and leverages well-audited libraries, resulting in a low technical risk profile. Key considerations include the centralized initial token distribution and the lack of emergency pause functionality, which are common design choices for simple tokens but noted for their implications.

Technical8/10Low risk

The technical architecture (7.1) of the HIGH token is straightforward, implementing the ERC-20 standard. Code security (7.2) is robust, primarily due to the reliance on OpenZeppelin's highly audited and widely used ERC-20 library. The custom logic is minimal and correctly implemented, utilizing Solidity 0.8.x which includes default overflow/underflow checks. Access control (7.3) is limited to the standard ERC-20 functions, with no additional administrative roles or complex permissions, which simplifies the security model.

Governance1/10High risk

The economic model (7.4) of the HIGH token is simple: a fixed total supply minted entirely at deployment. There are no mechanisms for inflation or deflation post-deployment, ensuring predictable supply. Governance (7.5) is not implemented within the contract itself, as it functions purely as a token. The initial distribution is centralized, with all tokens minted to a single address, which is a design choice that should be managed carefully. External dependencies (7.6) are minimal, limited to standard ERC-20 interactions, with no oracle or complex external calls.

Upgrades6/10Medium risk

The HIGH token contract is not designed with any upgradeability mechanisms (7.7). It is deployed as an immutable contract, meaning its logic cannot be changed post-deployment. This eliminates upgrade-related risks such as proxy misconfigurations or malicious upgrade paths, but also removes the flexibility to fix potential future issues or add new features. Operational risks (7.8) are primarily related to the correct deployment parameters, specifically the minter address.

Final RecommendationWhat to do about this score

The Highstreet Token contract is a well-structured ERC-20 implementation, benefiting significantly from its reliance on OpenZeppelin's battle-tested libraries.

The minimal custom logic further reduces the attack surface. Projects should ensure the minter address used during deployment is a secure, multi-signature wallet to mitigate risks associated with the centralized initial token distribution. While the contract's immutability provides security through predictability, consider the implications of lacking emergency response mechanisms like a pause function for future integrations or unforeseen events.

Contract & Record

1 audit on record
TypeToken
NetworkEthereum
Token age4y
Contract0x71ab…0282
Deployer0xba92…f26c
Badge for your website
Highstreet 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. Aug 16, 202640Medium

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

Related Audits

6 more on the recordAll audits
Artificial Superintelligence AllianceFET · Ethereum40MediumOndoEthereum40MediumRequest TokenREQ · Ethereum40MediumIdentity.mdIMD · Ethereum40MediumOutBurnEthereum40MediumWrapped GonkaWGNK · Ethereum40Medium

Would You Like a More Detailed Audit of Highstreet 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