Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 3d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILLP custody
- FAILHolder concentration
DexProof recorded KITTEN as CRITICAL on Robinhood Chain under formula v1.63, in verdict #1241 published 27 Oct 2026 (UTC). Of 28 checks, 15 passed, 1 warned, 4 failed and 8 could not be run.
Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 3d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
This token's creator removed liquidity from this token's pool.
It made 1 withdrawal on Uniswap V2, and that withdrawal closed the position completely.
The largest LP holder, (a smart-account wallet), controls 100.0% of this pool's liquidity and can withdraw it at any moment.
It is not the deployer. Renouncing ownership does not protect against this. None of this pool's liquidity is burned or locked.
Top 10 holders hold 97% of the tokens in circulation.
The largest holder is , a plain wallet, holding 63.9% of the tokens in circulation on its own. Against total supply, the top 10 hold 93.5%. Liquidity pools hold 3.7% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
The token contract has privileged powers: amm route change, fee change, exemption change, limit change.
Someone can still use them, or we couldn't tell who controls them.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
These are gaps in what we could see, not problems found in this token.
The creator's wallet was funded by , a shared source that has sent starting funds to 22 different wallets.
A shared source such as an exchange funds many unrelated people, so its record does not name any one of them.
This deployer was funded by , a wallet that has sent starting funds to 22 different wallets.
That is a shared source such as an exchange, so its history says nothing about this deployer.
The contract has no owner function, but we can't confirm nobody controls it.
Our contract audit could not tell who holds control over it.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
The token's main pool and every other pool large enough to matter let it be sold in our test.
This does not show how large a sale those pools can absorb, or that Uniswap's own router will carry it out.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
This deployer has no earlier launches on record.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer.
The code matches, but the compiler metadata does not.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This contract was 111 days old at this scan.
No launchpad deployed this token.
It was deployed directly, which counts neither for nor against it. The on-chain checks decide this one.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.