ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
1 VERDICT ON RECORD
16 points of this token's scoring surface could not be read this scan, so the score is capped at 84 (top of CAUTION). A check that stands down for want of data deducts nothing, so without this cap a failed read would read the same as a clean result. This is about our coverage, not about the token.
None of this V3 pool's liquidity is burned or locked. The largest liquidity provider — , a contract, NOT the deployer — holds 100.0% of the liquidity holding up the price. This contract is not a trusted locker, so this liquidity is not considered locked. Its controller or contract logic may still transfer or withdraw it; contract audit is required before making a stronger claim. This pool is on Uniswap V3 and backs 100.0% of the token's pooled liquidity.
Pool is 8.2h old, under the 48h line.
Contract deployed 8.2h ago.
No canonical asset collision.
EMOJI scores 84 — CAUTION. LP custody is the one that moved it, 9 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 V3 pool's liquidity is burned or locked. The largest liquidity provider — , a contract, NOT the deployer — holds 100.0% of the liquidity holding up the price. This contract is not a trusted locker, so this liquidity is not considered locked. Its controller or contract logic may still transfer or withdraw it; contract audit is required before making a stronger claim. This pool is on Uniswap V3 and backs 100.0% of the token's pooled liquidity.
No owner() function, and the contract audit did not complete, so ownerlessness is not established.
Not an upgradeable proxy. The code is fixed.
Contract source is partially verified on the explorer — a bytecode-database match, not an exact source match.
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.