ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
3 VERDICTS ON RECORD · MOVED -1 SINCE FIRST SCAN (84 → 83)
No market data, so liquidity cannot be measured.
59 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 32.2% of the circulating float. On raw total supply that's 14.2%, because 98.2% 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 plain wallet, holding 4.3% of the float on its own.
Contract deployed 6.2h ago.
No canonical asset collision.
Cyber Dog scores 83 — 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 (hookless) pool: 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.
LP locked: 100.0% of this V4 pool's liquidity is held by Uniswap v4 FeeSplitter, 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 100.0% 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 partially verified on the explorer, matched from another address with identical bytecode 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.