ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
3 VERDICTS ON RECORD · MOVED -18 SINCE FIRST SCAN (100 → 82)
None of this V4 pool's liquidity is burned or locked. The largest liquidity provider — , a plain wallet, NOT the deployer — controls 51.9% of the liquidity holding up the price and can withdraw it at any moment. Renouncing ownership does not protect against this. This pool is on Uniswap V4 and backs 14.0% of the token's pooled liquidity. The token's deepest pool (Uniswap V3, 71.9% of pooled liquidity) was assessed separately: an unclassified contract holds a controlling liquidity share; it is not proven locked.
No canonical asset collision.
No scam tag on the explorer.
Buy and sell both simulate cleanly, including as two independent fresh wallets.
No liquidity removal from this token's own pool. None in the deployer's recent history either.
MARIAN scores 82 — 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
Buy and sell both simulate cleanly, including as two independent fresh wallets.
None of this V4 pool's liquidity is burned or locked. The largest liquidity provider — , a plain wallet, NOT the deployer — controls 51.9% of the liquidity holding up the price and can withdraw it at any moment. Renouncing ownership does not protect against this. This pool is on Uniswap V4 and backs 14.0% of the token's pooled liquidity. The token's deepest pool (Uniswap V3, 71.9% of pooled liquidity) was assessed separately: an unclassified contract holds a controlling liquidity share; it is not proven locked.
Ownership renounced (owner is the zero/dead address).
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.