On-chain security analysis — is it a scam or legit?
PolygonThe contract is a standard OpenZeppelin TransparentUpgradeableProxy deployed on Polygon.
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 22, 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.
0xe65b…f6400x4dd6…30a60x957b…3eb30xb394…fd750x6dc3…15350xdc20…78ed0xf5a5…9da30x3d4c…111c0xa8e4…8ea40x3b23…a12d0.0% of the pool's LP is burned or time-locked. 99.0% is held, unlocked, by 10 address(es) other than the owner/deployer. One of them — a contract, 0xe65b…f640 — holds 59.8% 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 93.3% of supply. What remains: 4.9% in wallets, 88.4% in other contracts. 341,021 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
341,021 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 $18K (DexScreener, all pools). 24h trading volume $112K (DexScreener, 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: a single wallet (EOA). Code: upgradeable proxy. Fees: no buy or sell tax. Market: $18K of DEX liquidity across 1 pools. Launch: 483 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 OpenZeppelin TransparentUpgradeableProxy deployed on Polygon. It serves as a gateway to an underlying implementation contract. The proxy architecture is well-established, and no vulnerabilities were identified in the proxy logic itself. The security of the protocol depends entirely on the implementation contract, which is currently unverified.
The architecture follows the industry-standard EIP-1967 Transparent Proxy pattern. 7.1 Architecture is robust, utilizing a dedicated ProxyAdmin to separate administrative concerns from user interactions. 7.2 Code Security is high as the proxy logic is inherited from audited OpenZeppelin libraries. 7.6 External dependencies are limited to standard library interfaces.
7.3 Access Control is managed via an EOA-controlled ProxyAdmin, which is standard for this pattern. 7.4 Economic and 7.5 Governance risks are not applicable at the proxy level, as the proxy does not hold logic or state related to tokenomics. The security of these aspects is deferred to the implementation contract.
7.7 Upgrades are handled via the Transparent Proxy pattern, which prevents function selector clashes between the proxy and implementation. The upgrade mechanism is correctly implemented using the ProxyAdmin. 7.8 Operations are standard, with the owner having the ability to upgrade the implementation contract at any time.
The proxy contract is secure and follows best practices. However, because the implementation contract is unverified, users should exercise caution until the implementation source code is published and audited.
Ensure that the ProxyAdmin owner is a multi-signature wallet or a time-locked governance contract to mitigate risks associated with EOA-based administrative control.
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
