ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
3 VERDICTS ON RECORD · MOVED -24 SINCE FIRST SCAN (84 → 60)
None of this CL pool's liquidity is burned or locked. The largest liquidity provider is , a plain wallet. It controls 57.1% of this pool's liquidity and can withdraw it at any moment. Renouncing ownership does not protect against this. This pool is on Up CL and holds 90.6% of the liquidity this scan could read.
Top 10 holders hold 50.9% of the circulating float. On raw total supply that's 28.7%, because 43.6% of total supply sits in liquidity pools and is excluded from the float. The float figure is measured against supply outside the pools, so it also moves when pool liquidity moves. The single largest holder is , a contract, holding 8.9% of the float on its own.
55 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.
Deepest pool holds $6682.
24h volume is 18× liquidity.
COCKIN scores 60 — CAUTION. LP custody is the one that moved it, 18 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 (hookless) pool: exitable. A direct transfer probe also clears the token's own transfer layer, which the V4 Quoter alone cannot exercise.
None of this CL pool's liquidity is burned or locked. The largest liquidity provider is , a plain wallet. It controls 57.1% of this pool's liquidity and can withdraw it at any moment. Renouncing ownership does not protect against this. This pool is on Up CL and holds 90.6% of the liquidity this scan could read.
No owner() function. No single owner key surface.
Not an upgradeable proxy. The code is fixed.
The explorer that answered does not report source verification, so it could not be established either way.
No privileged capabilities found in the audited source and bytecode.
Explorer unreachable. Source data unavailable.
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.