DexProof recorded knightcat as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1279 published 27 Oct 2026 (UTC). Of 28 checks, 9 passed, 5 warned, 2 failed and 12 could not be run.
Don't trade this token.
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
Scanned 3d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
That wallet is , and it made 1 withdrawal on Uniswap V4, and that withdrawal closed the position completely.
This contract's source code is not verified on the explorer.
We couldn't finish the sell test on the other exchanges we checked.
We couldn't get a clear result from any pool we tested, so we can't say whether this token can be sold.
This token crashed after launch.
On 2026-10-07, its price or liquidity fell 95% or more below its 72-hour peak, and a second data source confirmed it. This often happens when early buyers sell. On its own it does not mean the contract or its liquidity is unsafe.
We are publishing this verdict because a critical finding was read directly.
Some checks could not be read on this scan, which would normally hold a verdict back. Missing data elsewhere cannot undo that finding.
This contract still has an active owner: .
The source is not verified, so the code can't be read.
We could not match it to a known template.
These are gaps in what we could see, not problems found in this token.
Applies to: Funder rug history, Deployer launch history, Funding lineage, Tax manipulation
So we can't check for past rugs, because many people launch through it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check its past launches. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't trace who funded it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check whether it changed fees or limits.
This pool has no liquidity at its current price, so there is no share of it to check.
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 couldn't identify 15 functions in this token's code, and it has published no source that names them.
They are 0x088cb857, 0x0bbefda6, 0x0c2d38aa, 0x16ecb8bd, and 11 more. So we can't say if any of them can mint, pause, blacklist or limit this token.
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.
A contract deployed this token, but that contract is not in the launchpad registry.
So we can't tell where it launched.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
Top 10 holders hold 2% of the tokens in circulation.
Against total supply, the top 10 hold 0.3%. Liquidity pools hold 76.5% 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.
This contract's code is fixed.
We found no standard upgrade setup on it.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 23 days old at this scan.
Robinhood