ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
2 VERDICTS ON RECORD · MOVED -18 SINCE FIRST SCAN (71 → 53)
The deployer (), a contract, holds 100.0% of the liquidity backing this V4 pool at the current price. This contract is not a trusted locker, so this liquidity is not considered locked. Its code was audited: `launch(TokenParams,uint256,uint256,uint256,bytes32)` can move that liquidity, and ownable can call it, so this share can be pulled at any moment. This pool is on Uniswap V4 and holds 99.8% of the liquidity this scan could read.
Top 10 holders hold 100.0% of the circulating float. On raw total supply that's 2.4%, because 97.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 plain wallet, holding 89.7% of the float on its own.
No market data, so liquidity cannot be measured.
Privileged capabilities present and reachable via a live or unresolved authority: fee change, supply mint, initialization.
69 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.
SKULL scores 53 — DANGER. 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 pool and its swap hook: 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.
The deployer (), a contract, holds 100.0% of the liquidity backing this V4 pool at the current price. This contract is not a trusted locker, so this liquidity is not considered locked. Its code was audited: `launch(TokenParams,uint256,uint256,uint256,bytes32)` can move that liquidity, and ownable can call it, so this share can be pulled at any moment. This pool is on Uniswap V4 and holds 99.8% of the liquidity this scan could read.
No owner() function, but the contract audit could not attribute the contract's authority surface, so ownerlessness is not established.
Not an upgradeable proxy. The code is fixed.
Contract source is verified on the explorer. Read at its implementation .
Privileged capabilities present and reachable via a live or unresolved authority: fee change, supply mint, initialization.
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.