Is Base Juice (BASEJUICE) Safe? Smart Contract Security Analysis

Security Findings

1 Info

Info

No issues identified in the reviewed source

I-01The 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.

IssueThe 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.

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

StatusAcknowledged

Category Ratings

TechnicalLow10/10

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.

GovernanceMedium5/10

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.

UpgradesMedium6/10

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.

Security Checklist

2/5 checks passed

Contract VerifiedPass

Ownership Renounced?

No Mint Function?

Liquidity LockedFail

Not a ProxyPass

HoneypotNoneBuy Tax0.0%Sell Tax0.0%

Holder Composition

22.1% in top 10

5.1% in wallets17.1% in contracts

Effective Concentration11.9%

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.

Liquidity Depth

$141.0K across 12 pairs

Uniswap v4ETHanalysed$119.4K Uniswap v4USDC$19.0K Uniswap v4USDC$1.3K Uniswap v4ETH$1.2K Uniswap v4ETH$53 Uniswap v4ETH$38

Show 4 more pairsShow less

Uniswap v4ETH$9 Uniswap v4USDC$8 Uniswap v4USDC$3 Uniswap v4USDC$1

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

Top-1 Unlocked Holder28.8%

Top-3 Unlocked68.2%

Key Addresses

10 addresses

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.

What Raised This Score

4 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

Is Base Juice Safe?