On-chain security analysis — is it a scam or legit?
This audit report is based on an analysis of the provided contract address without access to its verified source code.
Read the full analysisEach 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
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
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x0b23…1b140x1623…ab5b0xe254…8b8b0x8160…287d0x3dd5…599d0xf48e…29aa0xd9a2…3a88No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The contract at address on the Base network does not have its source code verified on the blockchain explorer. This prevents a thorough security audit and makes it impossible for users to understand the contract's logic and behavior.
Verify the full source code of the contract on the Base blockchain explorer. This increases transparency and allows for public scrutiny and security analysis.
Unresolved
Due to the absence of verified source code, static analysis tools and manual code review techniques cannot be applied. This means that common vulnerabilities such as reentrancy, integer overflows/underflows, access control flaws, or logic errors cannot be identified or confirmed.
Provide the complete and accurate source code for static analysis. This is a fundamental step in identifying and mitigating potential security vulnerabilities before deployment or during an audit.
Unresolved
Operating a protocol with unverified contract code introduces significant operational risks (7.8 Operations). It becomes impossible to monitor the contract's internal state changes, understand its dependencies, or react effectively to unexpected behavior or potential exploits, as the underlying logic is opaque.
Ensure all critical production contracts have verified source code. Implement robust monitoring solutions that can interpret contract events and state changes based on known, verified logic.
Unresolved
This audit report is based on an analysis of the provided contract address without access to its verified source code. Therefore, a comprehensive security assessment for vulnerabilities like reentrancy, integer overflows, or access control flaws could not be performed. The findings below are informational, highlighting the inherent risks associated with unverified contracts.
Without access to the contract's source code, a technical security analysis (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) cannot be performed. This prevents identification of common vulnerabilities such as reentrancy, integer overflows, or improper access controls. The lack of transparency significantly increases the technical risk, as the contract's logic and potential attack vectors remain unknown, making it impossible to assess its security posture.
The economic and governance aspects (7.4 Economic, 7.5 Governance) of the contract cannot be assessed without source code. This means potential risks like oracle manipulation, economic exploits, or centralized control mechanisms are unknown. The absence of transparency makes it impossible to evaluate the contract's resilience against economic attacks or its governance structure, posing significant economic and governance risks.
The upgradeability status and mechanisms (7.7 Upgrades) of the contract are unknown due to the lack of source code. It is impossible to determine if the contract is upgradeable, what proxy pattern (e.g., UUPS, Transparent) it might use, or if upgrade safety measures are in place. This introduces significant uncertainty regarding future changes and potential upgrade-related risks, as any upgrade path remains opaque.
It is strongly recommended that the source code for the contract at be verified on the Base blockchain explorer.
Without verified source code, users and auditors cannot ascertain the contract's intended functionality, security posture, or adherence to best practices. Engaging in any interaction with unverified contracts carries inherent and significant risks. For any smart contract deployment, ensuring full transparency through verified source code is a foundational security measure. This enables community review, professional audits, and allows for proper monitoring and incident response (7.8 Operations) based on known logic.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
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
