DexProof recorded OPOSS as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1445 published 28 Oct 2026 (UTC). Of 28 checks, 15 passed, 4 warned, 3 failed and 6 could not be run.
Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
This token's creator removed liquidity from this token's pool.
It made 1 withdrawal on Uniswap V4, and that withdrawal closed the position completely.
The largest liquidity provider, (a plain wallet), controls 39.5% of this pool's liquidity and can withdraw it at any moment.
It is not the deployer. Renouncing ownership does not protect against this. None of this V4 pool's liquidity is burned or locked. This pool is on Uniswap V4 and holds 86.2% of the liquidity we could read. 2 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
This exact code was used by 32 other tokens, and 30 of them lost most of their value or had their liquidity removed.
They include 0xde19…5ee5, 0xa918…3f22, 0x0c75…4202. That describes those tokens, and it does not say who created this one.
We couldn't finish the sell test on the other exchanges we checked.
At least one pool did not pass its sell test and could not be shown too small to matter, so we can't say this token can be sold everywhere. Sells on this pool go through a swap hook. The hook's owner is 0xfe8c…f495. Our code check found functions that let its owner set a router list, a whitelist or a blacklist. We can't see whether the owner has used them. Its code is identical to a hook template we have seen on other tokens on this chain. Details are under Pool Hooks.
This token crashed after launch.
On 2026-10-17, its price or liquidity fell 95% or more below its 72-hour peak, and a second data source confirmed it. This often happens when early buyers sell. On its own it does not mean the contract or its liquidity is unsafe.
We couldn't work out who controls this token's liquidity on this scan.
Missing data limits the verdict. A pool we couldn't read is not a pool we cleared. This describes what we could see, not the token.
Top 10 holders hold 48% of the tokens in circulation.
The largest holder is , a smart-account wallet, holding 29.6% of the tokens in circulation on its own. Against total supply, the top 10 hold 39.3%. Liquidity pools hold 18.2% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
These are gaps in what we could see, not problems found in this token.
We found no active rug markers in the funding records we checked, but we couldn't trace every wallet linked to this deployer.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
Nothing on record ties , the wallet that funded the creator, to a past rug on Robinhood Chain.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This deployer has no earlier launches on record.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer, matched from another address with identical bytecode, not proven against this one.
We found no mint, pause, blacklist or limit functions in the token contract's code.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This contract was 12 days old at this scan.
No launchpad deployed this token.
It was deployed directly, which counts neither for nor against it. The on-chain checks decide this one.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.
This token trades in V4 pools that run a hook, a contract that executes on swaps. Here is what Uniswap's public hook list says about each one. It describes the hook, not this token.
Its code is byte for byte the same as a hook template we have seen on other tokens on this chain.
Found by reading the hook's code. Whether the owner has used these controls is not something this scan can see.
We could not read Uniswap's hook list just now, so we cannot say whether this hook is described there.
Robinhood