Trade with care. Read the warnings first.
We found no Uniswap V3 pool paired with ETH, so we couldn't run a sell test there.
Scanned 2d ago. Scan again before you trade.
- WARNHoneypot
- WARNChecks with missing data
- WARNContract ownership
DexProof recorded UNI-V2 as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1366 published 28 Oct 2026 (UTC). Of 28 checks, 8 passed, 5 warned and 15 could not be run.
Trade with care. Read the warnings first.
We found no Uniswap V3 pool paired with ETH, so we couldn't run a sell test there.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
We found no Uniswap V3 pool paired with ETH, so we couldn't run a sell test there.
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.
The contract has no owner function, but our contract audit found something else that controls it: safe-multisig ().
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.
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.
We found no pool for this token on V2, V3 or V4, so there were no liquidity removals to read.
The LP custody check could not read this token's pools either, so we don't know who can pull its liquidity.
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 couldn't reach the chain's data service, so we couldn't check this.
Our data sources disagree on whether this contract's source is verified.
One says unverified, and another returns published source. We left it unresolved until they agree.
We couldn't find any functions in this token's code to check.
So we can't say if it can mint, pause, blacklist or limit this token.
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.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 69 days old at this scan.
This token has never traded, so there is no pool liquidity for us to check.
Applies to: Liquidity depth, FDV vs liquidity ratio, Volume turnover, Wash trading, Pool age
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.