Early-stage security check — honeypot & rug-pull analysis
0xca7a…6b05
No contract source code was provided for the address 0xca7a1e31b36779cf32acb18714ab26982cf36b05. Therefore, a comprehensive security audit could not be performed. The risk assessment below is based on the absence of information and should not be considered an actual evaluation of the contract's security posture.
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.
The 20 remaining pairs hold $8.6K between them and are not listed.
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.
0xe45a…a95a0xa471…cd470xd5a8…31a6No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
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
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit