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
- FAILLP custody
- FAILHolder concentration
DexProof recorded GP as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1522 published 29 Oct 2026 (UTC). Of 28 checks, 13 passed, 2 warned, 3 failed and 10 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 7 withdrawals on Uniswap V4, and 4 of them closed the position completely.
The largest liquidity provider, (a plain 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 V4 pool's liquidity is burned or locked. This pool is on Uniswap V4 and holds 100.0% of the liquidity we could read. 2 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
Top 10 holders hold 98% of the tokens in circulation.
The largest holder is , a contract, holding 39.8% of the tokens in circulation on its own. Against total supply, the top 10 hold 92.0%. Liquidity pools hold 6.3% 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. Some of these tokens sit inside a staking or escrow contract, and we could only partly tell who deposited them. We report the highest share the evidence supports.
We couldn't finish the sell test on the other exchanges we checked.
At least one pool did not pass its sell test and could not be shown too small to matter, so we can't say this token can be sold everywhere.
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.
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.
Launched on Collection Token Deployer.
We don't track this launchpad's raises yet, so we don't know how much of the raise the creator bought.
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 3 functions whose names match a standard OpenZeppelin contract. Some of them can hand out permissions or move tokens on someone's behalf, for example burnFrom. We matched the names, not what the code behind them does.
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 76 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.