ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
1 VERDICT ON RECORD
Deepest pool holds $0, effectively dead.
72 points of this token's scoring surface could not be read this scan, so the score is capped at 84 (the top of CAUTION). A check that stands down for want of data deducts nothing, so without this cap a failed read would look the same as a clean result. This is about what we could see, not about the token.
Active owner key: .
The same contract template has been deployed 3 times, a copycat pattern.
Pool is 0.1h old, under the 48h line.
DIME scores 77 — CAUTION. Liquidity depth is the one that moved it, 10 points off. Ask me why.
DRAWN FROM THIS VERDICT’S CHECKS — NOT A MODEL ANSWER
OPENS THE PANEL — THAT IS WHERE YOU TYPE
Sell quotes through the pool and its swap hook, and a full round trip recovers 97.0% of the probe: exitable. But the V4 Quoter does not settle token balances, and the token's own transfer layer could not be probed (could not locate the balances storage slot (non-standard layout), so no transfer could be simulated) — so nothing here exercised the layer where a sell is actually blocked, and no exit conclusion is drawn.
This pool's liquidity events do not reconcile with the liquidity the pool reports, so the event history is incomplete and no custody share can be trusted. This pool is on Uniswap V4 and holds 100.0% of the liquidity this scan could read.
Active owner key: .
Not an upgradeable proxy. The code is fixed.
Contract source is partially verified on the explorer — the code matches, the compiler metadata does not. Read at its implementation .
No mint/pause/blacklist/limit functions found in bytecode.
No fee or limit toggling by the deployer in the transactions searched. This looks at the deployer's recent history only, so calls by a separate fee authority are out of its reach.
Heads up: the scanner is improved continuously, and some fixes only surface once they meet real tokens on production. Our trusted registry — verified LP lockers, known-good launchpad contracts — is checked and approved by a human on the team, so a legitimate project can score lower for a while until we've confirmed its contracts ourselves. A low score is a prompt to look closer, not a conclusion.
Ask why this verdict reads the way it does.