Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 2d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILHolder concentration
- WARNHoneypot
DexProof recorded VRAX as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1429 published 28 Oct 2026 (UTC). Of 28 checks, 15 passed, 4 warned, 2 failed and 7 could not be run.
Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
This token's creator removed liquidity from this token's pool.
It made 1 withdrawal on Uniswap V3, and that withdrawal closed the position completely.
Top 10 holders hold 91% of the tokens in circulation.
The largest holder is , a plain wallet, holding 88.5% of the tokens in circulation on its own.
We couldn't finish the sell test on the other exchanges we checked.
The token's main pool did not pass a sell test, so smaller pools that did pass can't show the token can be sold.
This token crashed after launch.
On 2026-10-01, 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 couldn't work out who controls this token's liquidity on this scan.
Missing data limits the verdict. A pool we couldn't read is not a pool we cleared. This describes what we could see, not the token.
The largest liquidity provider, (a contract), holds 100.0% of this pool's liquidity.
It is not the deployer. This contract is not a trusted locker, so this liquidity is not considered locked. Its controller or contract code may still move or withdraw it. The contract needs an audit before we can say more. None of this V4 pool's liquidity is burned or locked. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there. This token trades in 6 pools. We couldn't measure their sizes, so the pool named here may not be its main market. The full pool list is in the evidence.
These are gaps in what we could see, not problems found in this token.
We found no active rug markers in the funding records we checked, but we couldn't trace every wallet linked to this deployer.
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 an unregistered launchpad, but we don't know how that launchpad works, so we can't say whether there was a raise for the creator to buy into.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
Nothing on record ties , the wallet that funded the creator, to a past rug on Robinhood Chain.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This deployer has no earlier launches on record.
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 verified on the explorer, but it was matched from another address with identical bytecode, not proven against this one.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
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 28 days old at this scan.
The source is verified, so anyone can read the code.
We could not match it to a known template.