ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
4 VERDICTS ON RECORD · MOVED +28 SINCE FIRST SCAN (56 → 84)
No supported WETH V3 pool exists, so buy/sell simulation is unavailable.
28 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 39.4% of the circulating float. On raw total supply that's 30.8%, because 21.9% 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 10.4% of the float on its own.
Pool is 13.7h old, under the 48h line.
Contract deployed 16.7h ago.
OBEX 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
No supported WETH V3 pool exists, so buy/sell simulation is unavailable.
Pool discovery was incomplete: the uniswap-v4 leg did not answer whole, so the pool set may be missing a pool and no pool's share of it can be trusted.
No owner() function, and the contract's source could not be verified — the explorer did not answer — so its authority surface could not be enumerated and ownerlessness is not established.
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 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.