ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
1 VERDICT ON RECORD
32 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.
Top 10 holders hold 41.1% of the circulating float. On raw total supply that's 26.6%, because 35.1% 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 12.6% of the float on its own.
No canonical asset collision.
No scam tag on the explorer.
Sell quotes through the pool and its swap hook: exitable. A direct transfer probe also clears the token's own transfer layer, which the V4 Quoter alone cannot exercise.
RHCAT scores 84 — CAUTION. Holder concentration is the one that moved it, 5 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: exitable. A direct transfer probe also clears the token's own transfer layer, which the V4 Quoter alone cannot exercise.
LP locked: 100.0% of this V4 pool's liquidity is held by Launchpad V2 Launch Locker, a trusted locker contract, and the lock is permanent, so that liquidity can never be withdrawn and only its trading fees can be collected. This pool is on Uniswap V4 and holds 99.6% of the liquidity this scan could read.
No owner() function. No single owner key surface.
Not an upgradeable proxy. The code is fixed.
Contract source is verified on the explorer, but matched from another address with identical bytecode (a shared bytecode database) rather than proven against this one.
No privileged capabilities found in the audited source and 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.