No Solidity source code was provided for analysis of the contract at 0xb200000000000000000000b8d3746d2e56596578. Therefore, a comprehensive security audit could not be performed. The assessment is based solely on the provided metadata, and no specific vulnerabilities can be identified without code access.
On-chain security analysis — is it a scam or legit?
Is KittehCoin Safe?
Not verified
This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →No Solidity source code was provided for analysis of the contract at 0xb200000000000000000000b8d3746d2e56596578. Therefore, a comprehensive security audit could not be performed.
Read the full analysis- Ownership status UNKNOWN
- Mint capability UNKNOWN
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 55.3%
- LP top3 unlocked holders = 97.6%
Exact factors
- Ownership status UNKNOWN (owner could not be resolved)
- Mint capability UNKNOWN (implementation ABI unreadable)
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 55.3% (independent LP — depth risk, pool = 81% of DEX liquidity)
- LP top3 unlocked holders = 97.6% (independent LP — depth risk, pool = 81% of DEX liquidity)
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
Security Checklist
as of audit · Sep 4Holders
as of audit · Sep 4, 2026- Contractstreasury, vesting, bridge, staking19.2%
- Walletsanonymous holders, free to sell4.8%
- Everyone elsethe rest of the supply76.0%
How holder types affect the score
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
Liquidity
as of audit · Sep 4- Uniswap v4ETHAnalysed$48.3K80.7%
- Uniswap v4USDC$7.7K12.8%
- Uniswap v4USDC$3.7K6.1%
- Uniswap v4ETH$1170.2%
- Uniswap v4USDC$710.1%
- Uniswap v4USDC$180.0%
The 3 remaining pairs hold $2 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.
0x76c8…055b0xb1b7…e1410xcc2b…49070x02f4…30b50x3a93…73e70x8a22…6c400x85f9…ea620xd0f5…48170x5a01…a6920xeed6…d767No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
InfoMissing Source Code for Analysis
The Solidity source code for the contract at 0xb200…6578 was not provided. This prevents any form of static or dynamic analysis, making it impossible to identify potential vulnerabilities, assess code quality, or verify adherence to security best practices.I-01
Issue
The Solidity source code for the contract at was not provided. This prevents any form of static or dynamic analysis, making it impossible to identify potential vulnerabilities, assess code quality, or verify adherence to security best practices.
Fix
Provide the complete and verified Solidity source code for the contract. This should include all imported libraries and dependencies. Verification on block explorers is highly recommended to ensure the deployed bytecode matches the provided source.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4No Solidity source code was provided for technical analysis, preventing any assessment of architectural design, code security, or access control mechanisms. Without source code, it is impossible to identify common vulnerabilities such as reentrancy, integer overflows, or logic errors (7.1, 7.2, 7.3). The absence of code means no technical strengths can be identified, and all potential technical risks remain unknown, including interactions with external contracts (7.6).
The economic model and governance mechanisms of the contract could not be evaluated due to the absence of source code. This prevents any assessment of potential economic vulnerabilities, flash loan attack vectors, or the robustness of governance processes (7.4, 7.5). Without code, no economic or governance strengths can be determined, leaving all related risks unverified.
The contract's upgradeability status and associated risks could not be determined without source code. It is unknown if the contract utilizes a proxy pattern (e.g., UUPS, Transparent) or is immutable (7.7). This prevents an assessment of upgrade safety, potential risks associated with future changes, and operational considerations (7.8). No strengths in upgradeability or operations can be identified without code.
To enable a comprehensive security assessment, it is crucial to provide the full Solidity source code for the contract at . Without source code, no meaningful security guarantees can be provided, and potential vulnerabilities remain unknown.
Ensure all deployed code is verified on block explorers to enhance transparency and allow for public scrutiny.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Sep 4, 202623Low
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Would You Like a More Detailed Audit of KittehCoin?
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