Quantum Audit Logo
Launch App

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

Is Base Juice Safe?

BASEJUICEBase
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

This audit report is generated without access to the smart contract's source code.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Mint capability UNKNOWN
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • Token age < 30 days
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Mint capability UNKNOWN (implementation ABI unreadable)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • Token age < 30 days (still settling)

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 7 checks passed
Contract verifiedVerified
OwnershipUnknown
MintUnknown
Liquidity lockNot locked
UpgradeabilityFixed code
HoneypotNone found
Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026
17.1%Contracts5.1%77.9%Everyone else
17.1%5.1%77.9%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
22.1%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking17.1%
  • Walletsanonymous holders, free to sell5.1%
  • Everyone elsethe rest of the supply77.9%
Effective concentrationwhat the score reads11.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$141.0K across 12 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$119.4KShare of depth84.7%
Top-1 Unlocked Holder28.8%
Top-3 Unlocked68.2%
Unlocked LP held by
0x9a8c…44e80x4c12…da0a0x5004…4d870x3b0c…3fcd0xcf95…207f0x1b34…3e960x4ff4…0c710xe025…01c90xc3e0…31bd0xef7a…ae3b

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

Security Findings

1 Info
Info

No issues identified in the reviewed source

The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (holder concentration) were applied separately and feed the risk score.I-01

Issue

The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (holder concentration) were applied separately and feed the risk score.

Fix

Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.

Status

Acknowledged

Analysis

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

This audit report is generated without access to the smart contract's source code. Therefore, a comprehensive security analysis for the contract at address 0xb200000000000000000000046390aed221043f01 on the Base network could not be performed. All risk levels and findings are set to 'N/A' or 'Low' by default due to the absence of code for review.

Technical10/10Low risk

Without access to the contract's source code, a technical assessment of its architecture (7.1), code security (7.2), and access control mechanisms (7.3) is not possible. Therefore, no specific strengths or issues can be identified in this section. A thorough review would typically involve analyzing reentrancy guards, integer overflow/underflow protections, and proper permissioning.

Governance5/10Medium risk

An evaluation of economic factors (7.4) and governance mechanisms (7.5) cannot be performed without the contract's source code and a clear understanding of the protocol's design. This includes assessing potential for oracle manipulation or flash loan attacks, as well as the robustness of any decentralized governance structures. External dependencies (7.6) also remain unassessed.

Upgrades6/10Medium risk

The upgradeability aspects (7.7) of the contract, including the use of proxy patterns (e.g., UUPS, Transparent) and their associated risks, cannot be determined without the source code. Operational procedures (7.8) related to upgrades also remain unknown. A proper assessment would confirm the safety and security of any upgrade path.

Final RecommendationWhat to do about this score

For any future deployments or interactions with this contract, it is strongly recommended to obtain and verify the full source code.

A comprehensive security audit should then be conducted to identify and mitigate potential vulnerabilities across all technical, economic, governance, and upgradeability aspects. Ensure all external dependencies are well-understood and trusted.

Contract & Record

1 audit on record
Type-
NetworkBase
Token age14d
Contract0xb200…3f01
Badge for your website
Base Juice 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, 202615Low
  2. Aug 30, 202624Low

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

Frequently Asked Questions

What is the BASEJUICE contract address?

The Base Juice (BASEJUICE) contract on Base is 0xb200000000000000000000046390aed221043f01. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.

Is Base Juice a scam?

Quantum Audit's risk score for Base Juice is 15/100 (Low risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Liquidity lock: Not locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 0% / 0%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.

Is BASEJUICE liquidity locked?

Liquidity lock: Not locked (as of Sep 4, 2026). Total DEX liquidity: $141.0K.

Who holds BASEJUICE?

As of Sep 4, 2026, the 10 largest holders own 22.1% of the supply. The Holders section on this page shows who they are by holder type.

Would You Like a More Detailed Audit of Base Juice?

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