On-chain security analysis — is it a scam or legit?
No Solidity contract source code was provided for analysis. Therefore, a comprehensive security audit could not be performed.
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 5, 2026
The 15 remaining pairs hold $2.6K between them and are not listed. 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.
0x3533…c33c0x04c5…0df50x713b…3d410xd278…b2c20xdc86…5d100xeed7…03af0x06a8…701f0x5325…44ec0x896c…fc380xb96b…463cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The audit request did not include any Solidity contract source code. As a result, a detailed security analysis of the contract's implementation, logic, and potential vulnerabilities could not be performed. All risk assessments and findings are therefore based on the absence of information.
To receive a comprehensive security audit, please provide the complete and verified Solidity source code for the contract at address . This will enable a thorough review of all technical, economic, governance, and upgradeability aspects.
Unresolved
No Solidity contract source code was provided for analysis. Therefore, a comprehensive security audit could not be performed. The report fields reflect this lack of input, with risk levels and findings marked as N/A or informational. To conduct a proper audit, the full source code is required.
Due to the absence of contract source code, a technical security analysis (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) could not be performed. No assessment of reentrancy, integer overflows, or other common vulnerabilities was possible. Without code, no strengths or weaknesses in implementation can be identified.
Without the contract's source code, an evaluation of economic models (7.4 Economic) and governance mechanisms (7.5 Governance) is not feasible. It is impossible to assess potential oracle manipulation, flash loan vulnerabilities, or the robustness of any administrative controls. Similarly, external dependencies (7.6 External) cannot be identified or analyzed.
The upgradeability aspects (7.7 Upgrades) and operational procedures (7.8 Operations) of the contract cannot be determined without access to the source code. It is unknown if the contract employs a proxy pattern, if upgrade paths are secure, or if multi-signature controls are in place for critical operations. Therefore, no assessment of upgrade safety or operational risks can be made.
To ensure the security and integrity of any smart contract, a thorough audit of its complete source code is essential.
This process identifies potential vulnerabilities, ensures adherence to best practices, and mitigates risks before deployment. It is strongly recommended to provide all relevant contract code for a comprehensive security review.
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
