Don't trade this token.
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
- FAILDeployer pulled liquidity
- FAILDangerous functions
- WARNHoneypot
DexProof recorded LAPTOP as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1669 published 30 Oct 2026 (UTC). Of 28 checks, 10 passed, 5 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.
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.
The token contract has privileged powers: supply mint, initialization, address block, privileged low-level code we couldn't read, upgrade code.
Someone can still use them, or we couldn't tell who controls them.
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.
This contract still has an active owner: .
The code can be changed, but we found no admin address for it.
That does not prove the power to change it is gone. Another upgrade route may still be live.
This token's code matches an earlier creator liquidity removal on 0xbf3f…eac7.
We haven't verified that the same creator is behind both.
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.
Top 10 holders hold 26% of the tokens in circulation.
Against total supply, the top 10 hold 4.8%. Liquidity pools hold 81.9% 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 source is verified on the explorer, but it was matched from another address with identical bytecode, not proven against this one.
This is about its implementation at .
No paid promotion found on DexScreener.
This contract was 52 days old at this scan.
The source is verified, so anyone can read the code.
We could not match it to a known template.