Don't trade this token.
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
Scanned 1d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILHolder concentration
- WARNHoneypot
DexProof recorded WhiteWhale as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1593 published 29 Oct 2026 (UTC). Of 28 checks, 13 passed, 2 warned, 2 failed and 11 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 1d 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.
Top 10 holders hold 87% of the tokens in circulation.
The largest holder is , a plain wallet, holding 57.9% of the tokens in circulation on its own.
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.
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.
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 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.
This token has no pump-and-dump mark in our records.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer, matched from another address with identical bytecode, not proven against this one.
We found no mint, pause, blacklist or limit functions in the token contract's code.
It also has 1 function we couldn't identify (0x3c130d90). You may want to look at it. The contract's own published source names every one of them.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 21 days old at this scan.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.