On-chain security analysis — is it a scam or legit?
The contract is a standard ERC1967Proxy implementation. Static analysis confirms the ownership has been renounced, meaning no administrative functions are currently active.
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 Oct 30, 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.
0x2cc3…045a0x8bfd…b54b0xd2ef…da49No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 2 address(es) other than the owner/deployer. One of them — a wallet, 0x2cc3…045a — holds 99.4% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
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 (mint/owner authority, holder concentration) were applied separately and feed the risk score.
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Acknowledged
The ten largest holders own 33.9% of supply. Of that, 22.8% burned — not holders that can sell, so excluded from the concentration score. What remains: 5.2% in wallets, 6.0% in other contracts. 39,324 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
39,324 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $2.6M (GeckoTerminal, all pools). 24h trading volume $37K (GeckoTerminal, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: mint capability could not be read. Control: nobody (ownership renounced). Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $2.6M of DEX liquidity across 11 pools. Launch: 415 days of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The contract is a standard ERC1967Proxy implementation. Static analysis confirms the ownership has been renounced, meaning no administrative functions are currently active. The implementation contract source is not verified, limiting visibility into the underlying logic, but the proxy itself adheres to standard EIP-1967 patterns.
The architecture follows the standard EIP-1967 proxy pattern, ensuring clear separation between the proxy and implementation. 7.1 Architecture is robust, utilizing standard storage slots to prevent collisions. 7.2 Code Security is maintained by the simplicity of the proxy logic, which lacks complex state-changing functions. 7.3 Access Control is effectively disabled due to the renounced ownership status.
7.4 Economic and 7.5 Governance factors are not applicable as the contract acts solely as a transparent proxy. There are no internal economic parameters or governance mechanisms present. 7.6 External dependencies are limited to the implementation contract, which is currently opaque.
7.7 Upgrades are technically possible via the proxy pattern, but the renounced ownership prevents any further modifications to the implementation address. 7.8 Operations are stable as the contract is immutable in its current state. The lack of verified implementation source code remains the primary operational transparency concern.
Since the ownership has been renounced, the contract is effectively immutable.
Users should verify the implementation contract at the provided address to ensure the underlying logic aligns with expected behavior, as the proxy itself only facilitates delegation.
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? Add your links and get it Verified
