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 V4 pool's liquidity is burned or locked. The largest liquidity provider — , a plain wallet, NOT the deployer — controls 100.0% 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 51.6% of the token's pooled liquidity.
Top 10 holders hold 97.2% of the circulating float. On raw total supply that's 95.2%, because 2.0% of total supply sits in liquidity pools and is excluded from the float. The single largest holder is , a contract, holding 82.3% of the float on behalf of holders this scan could not enumerate — that share is not proven to be under one key. Some of this supply is held inside a staking or escrow contract whose depositors could only be partly identified, so this share is reported at its highest supported reading.
FDV is 45× liquidity.
Pool is 0.2h old, under the 48h line.
No canonical asset collision.
GP scores 65 — 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 100.0% 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 51.6% 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.