Robinhood Chain Honeypot Checker

Start from the exact chain and address

Copy the token contract address from the Robinhood Chain explorer, confirm the chain ID is 4663 and paste it into the scanner form on this page. Names and tickers are easy to copy, so a look-alike token can pass a check that the real one would fail, or the reverse.

This page uses the same scanner and the same pricing as the Robinhood Chain Token Scanner. There is no separate honeypot product and no extra charge for the honeypot checks inside a full analysis.

Honeypot, liquidity pull or insider dump

These three outcomes can all damage a buyer's exit, but they leave different evidence. A honeypot blocks or penalises the sell itself, through token code such as a blacklist, a pause switch, a balance rewrite or a punitive sell tax, or through pool logic. A liquidity pull removes pool liquidity, leaving little or no viable exit even when the token contract allows transfers. An insider dump is a large holder selling into buyers; the sell path may remain available while the price falls.

A honeypot check speaks to the first case. For the second, read the launch-position lock and liquidity evidence on the rug risk scanner page. For the third, read holder concentration, which stays partly unknown until common control between wallets is reviewed.

What the scanner checks automatically

For every supported token: GoPlus contract flags for honeypot behaviour, buy restrictions, mint, blacklist, pause, balance rewrite, proxy and published source; the dominant Uniswap V4 pool; a bounded raw holder list; and token-wide price candles. Each flag is reported as pass, fail or unknown with the time it was read.

For recognised, reviewed Pons V2 launch-family deployments only, the scanner also runs read-only buy, approve and sell simulations at a pinned block with inputs of 0.001, 0.01 and 0.05 ETH. The sender is funded synthetically; no private key is used, nothing is signed and nothing is broadcast. The same adapters match the factory, hook and locker code, and read the hook admin or owner and whether the launch position is locked.

Tokens outside those reviewed adapters, proxied contracts and simulations that fail to run are shown as unknown. MemeAssist does not route every V3 pool, every V4 pool or every hook through a simulation, and it does not perform a full static audit of contract bytecode. Other tools may advertise broader generic simulation or function-signature inspection; our automated coverage is deliberately narrower and is labelled as such.

Reading a simulation result

A successful simulated sell shows that, at that block and size, the sell path returned ETH. It is dated evidence, not a promise that you will be able to sell later. Owners, hooks, taxes and liquidity can change after the snapshot.

A failed or reverted sell is a reason to stop and investigate, not proof of fraud. Sells can fail because of a high transfer tax, thin liquidity, an RPC error, a missing allowance or a routing problem. The report shows the simulation status and the returned amount so you can tell a near-zero return from an outright revert.

Equally, a chart with no sells does not prove a honeypot. Very new or very quiet tokens may simply have no sellers yet.

Permissions show capability, not intent

A hook or token permission tells you what an address could do, such as change a fee or freeze transfers. It does not tell you whether anyone will. Treat a live permission as risk you are accepting, and its absence as one less route, not as safety.

A renounced owner does not rule out control. Upgradeable proxies, separate admin slots and role-based permissions can survive renouncement, which is why proxy status and hook admin are separate checks.

Liquidity locks and team tokens are different questions

On Uniswap V4, liquidity is held as concentrated-liquidity positions, each represented by an NFT with its own price range. A lock covers specific positions. The scanner reports whether the launch position is locked; it does not know what share of the whole pool is locked, because later positions can be added and withdrawn freely. Any lock percentage only means something once you know its denominator.

Team-token vesting is a separate question from liquidity locks. A locked launch position says nothing about when team or insider wallets can sell their tokens, and generalised vesting stays unknown in the report.

Manual checks worth doing yourself

On Blockscout, open the token contract: check whether the source is published, whether it is a proxy and, if so, which implementation it points to and who can upgrade it. Look for owner, admin and role functions. Published source is easier to read, not a sign of safety.

In the transaction list, look for sells from ordinary wallets into the pool, not just transfers between wallets. Transfers can succeed while sells are blocked.

For any lock, find the locker contract and note the lock owner, the beneficiary, the expiry and any early-withdrawal or migration function. A lock with an escape hatch is a promise, not a guarantee.

For holders, exclude the pool, locker and burn addresses, then note where the list was cut off and which wallets may share an owner. Write down what you could not confirm alongside what you could.

Scores, price and scope

Health and Rug Risk are provisional evidence indices, not fraud probabilities. The first full analysis is free for eligible new accounts and is shared across MemeAssist scanners; later scans use account credit at the price shown before you submit. MemeAssist is an independent analysis tool. It is not affiliated with, endorsed by or operated by Robinhood Markets.

Questions