ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
1 VERDICT ON RECORD
None of this V3 pool's liquidity is burned or locked. The largest liquidity provider is , a contract, and not the deployer. It holds 100.0% of this pool's liquidity. This contract is not a trusted locker, so this liquidity is not considered locked. Its code was audited: `collectFees(address)` can move that liquidity, and ownable can call it, so this share can be pulled at any moment. This pool is on Uniswap V3 and holds 100.0% of the liquidity this scan could read.
Unverified contract source.
32 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.
Pool is 1.1h old, under the 48h line.
Contract deployed 1.1h ago.
PCC scores 66 — 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 paying this chain's live gas price (45164000 wei).
None of this V3 pool's liquidity is burned or locked. The largest liquidity provider is , a contract, and not the deployer. It holds 100.0% of this pool's liquidity. This contract is not a trusted locker, so this liquidity is not considered locked. Its code was audited: `collectFees(address)` can move that liquidity, and ownable can call it, so this share can be pulled at any moment. This pool is on Uniswap V3 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.
Unverified contract source.
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.