The checker is in beta. Its accuracy has not been measured, nothing here is a guarantee, and a clean scan is evidence rather than a verdict.
What is a honeypot, exactly?
A honeypot is a token you can buy but cannot sell. The contract permits inbound swaps and blocks outbound ones — through a blacklist applied after purchase, a sell tax set near 100%, a transfer function that reverts for everyone except whitelisted wallets, or logic that only activates once enough victims are in. The chart looks healthy because every transaction is a buy. The trap is invisible until you try to leave.
Honeypots are the dominant scam pattern on new, high-velocity chains because they scale: the scammer deploys hundreds of variants, seeds each with a little liquidity, and waits. On Robinhood Chain, where memecoins drive the bulk of trading activity, the environment is exactly what this pattern feeds on. A rug pull drains a pool once; a honeypot farms buyers continuously until someone notices nobody has ever sold.
The defense is sequencing. Every check below happens before the swap. After you've bought, none of this helps.
The tool
Beta software. Do not rely on this.
This is an unfinished, unaudited experiment. Its accuracy has never been measured against a test set. It has not been reviewed. It will be wrong sometimes, in both directions: it will clear tokens that go on to rug, and it will flag tokens that are perfectly fine.
Nobody stands behind these results. No warranty of any kind is given, no claim of accuracy is made, and no responsibility is accepted for any decision you make after reading them. A clean result is not a recommendation, not an endorsement, and not financial advice. Do your own research and assume you can lose everything.
Setup & advanced — you usually don't need this
- RPC endpoint
- /api/rh-rpc (server-side proxy)
- V3 router
- 0xcaf681a66d020601342297493863e78c959e5cb2 published
- V3 factory
- 0x1f7d7550b1b028f7571e69a784071f0205fd2efa published
- WETH
- 0x0bd7d308f8e1639fab988df18a8011f41eacad73
- USDG
- 0x5fc5360d0400a0fd4f2af552add042d716f1d168
- PoolManager
- 0x8366a39cc670b4001a1121b8f6a443a643e40951 unverified — third-party source
- StateView
- 0xf3334192d15450cdd385c8b70e03f9a6bd9e673b unverified — third-party source
- Position manager
- 0x73991a25c818bf1f1128deaab1492d45638de0d3 published
- Explorer
- https://robinhoodchain.blockscout.com
- Trade size
- 0.01 ETH
- V4 hooks probed
- 0x0000000000000000000000000000000000000000, 0x2380abf72c17aabab76480244759ac7e2932eecc
- Chain check
- chain false · state overrides false · V4 false
What you get: a green, amber or red verdict per check with an overall rating, the contract's Blockscout page, and — where relevant — the owner and hook addresses, linked so you can read them yourself.
How the checker works
Most static scanners read a contract and infer. This one tries to sell.
It simulates buying the token and selling it straight back inside a single read-only call against live chain state, using a throwaway contract injected at call time. Nothing is broadcast, no wallet is connected, and no funds move. If the buy succeeds and the sell fails, that is the honeypot signature — and the checker reports what the contract said when it refused.
Eight checks, in the order that matters:
- Can you actually sell it? — a simulated buy and sell on Uniswap V3 or V4
- Is it actually tradeable? — pool discovery across V3 and V4 fee tiers
- Can they print more tokens? — mint entrypoints in the bytecode and, where published, the ABI. This works even when the source is unverified.
- Can the team still change the rules? — ownership, renouncement, upgradeable proxies
- What else can the owner do? — blacklist switches, trading gates, wallet limits
- What can the pool's hook do? — Uniswap V4 hook permissions
- Can anyone read the code? — source verification on Blockscout
- Is the liquidity locked? — answered honestly: the checker cannot tell you
Why a failed sell isn't always a scam
Some tokens charge a fee on every transfer. Uniswap V3 cannot process those at all — the swap reverts, and to a naive checker that looks identical to a honeypot. This checker reads the reason the contract gave. A pool reporting it was underpaid means a transfer fee, and the result says so. A token refusing the transfer outright is the real honeypot signature, and gets flagged as one. Being wrong in that direction has a cost: it brands ordinary taxed tokens as scams.
What a Uniswap V4 hook can do
Uniswap V4 lets a pool run custom code on every trade. That code can take a cut of each swap, block a sale, or stop liquidity being withdrawn — while the token contract itself looks completely ordinary. V4 encodes what a hook is permitted to do in the last bits of the hook's own address, so the checker reads those permissions directly and tells you what the pool's hook is allowed to do before you trade against it.
The honest limit. A simulated trade is much harder to fool than a static read, but it is not proof. A contract can behave normally for the checker and change its mind later — honeypots that switch on at a block height, or after the owner flips a setting, will pass a scan taken before they activate. The scan describes one moment. Run the manual checklist anyway.
Why the checker can't tell you if liquidity is locked
On Uniswap V3 and V4, liquidity is an NFT position rather than a token with a supply, so there is nothing to measure against burn addresses. Working out what share of a pool is locked means indexing the chain, which the checker does not do. It says “can’t tell” rather than guessing, because a wrong answer here is worse than no answer.
Team Finance holds that data, since it is the vault doing the locking. If you are launching, locking there is what makes your lock checkable by anyone. Our Robinhood Chain liquidity locks guide walks through how to read a lock page.
Lock your liquidity with Team Finance → team.finance/liquidity-locks
Manual rug check: how do you check a Robinhood Chain token without the tool?
This checklist needs nothing but Blockscout and the Team Finance site. It works today, works if our tool is down, and covers ground no automated scan reaches. Run all seven.
- Check who owns the liquidity position. On Uniswap V3 and V4 liquidity is an NFT, not a fungible LP token, so there is no holder list to read. Open the position in the position manager contract and look at its owner. An ordinary wallet can withdraw that liquidity at any moment. A locker contract with no withdraw function cannot — which is stronger than a timed lock, but you have to read the contract to know which you have.
- Open the contract on Blockscout and check for verification. Address bar →
robinhoodchain.blockscout.com→ paste the contract. No published source code, no buy. - Search the source for supply and control functions. Look for
mint,blacklist,setTaxor fee setters,pause, and transfer restrictions. You don't need to be a developer — the function names are usually plain, and their presence is the finding. - Check ownership. On the contract's read tab, look up the
owner. The zero address (0x000…000) means renounced. A live owner plus dangerous functions from step 3 equals a standing threat. - Look for real sells. Open the token's transfer history and find sales — swaps from ordinary holder wallets back to the pool. Many buys and no sells from anyone but the deployer is the honeypot signature, visible in public data.
- Check holder concentration. Open the holders tab. If a few non-vault wallets control most of the supply, one decision ends the market — no contract trickery required.
- Verify the team's own tokens are locked or vested. A locked pool with an unlocked team allocation just changes which rug you get. Look for team token locks and vesting on Team Finance.
Five minutes, every token, every time. The routine matters more than any single check — and if you're new to buying on this chain, start with our how to buy on Robinhood Chain guide, which builds this verification into the purchase flow itself. For the deeper reasoning behind each signal, see how to tell if a Robinhood Chain token is safe.
If you're a builder: pass the check before anyone runs it
Every check on this page has a mirror image for token creators. Buyers are running these scans on your token today — the strongest move is to make every light green before launch: verify your contract, fix your supply, lock your liquidity, and lock your team allocation. A burned or locked pool, a verified fixed-supply contract, and a public Team Finance lock page turn a skeptical buyer's five-minute check into your best marketing asset. Rug-proof by design beats rug-checked after the fact.
FAQ: Robinhood Chain honeypot and rug checks
Does honeypot.is work for Robinhood Chain tokens? No — honeypot.is does not support Robinhood Chain, so pasting a Robinhood Chain address there returns nothing useful. That is why this checker exists: it is built for chain 4663 and simulates a real buy and sell against the token’s own Uniswap V3 or V4 pool on this chain, and decodes V4 hook permissions. You can also check manually on Blockscout at robinhoodchain.blockscout.com, and check lock status on Team Finance.
Does this checker actually try to sell the token? Yes — in a simulation against live chain state. It buys and sells straight back inside a single read-only call, with nothing broadcast and no wallet needed.
Why does it sometimes say it can’t tell? Because some questions cannot be answered from a single read — liquidity lock share being the main one — and it would rather say so than guess.
Can a honeypot checker guarantee a token is safe? No, and any tool claiming certainty is overselling. Automated checks catch mechanical red flags — unverified code, mint functions, live owner keys, a sell that reverts. They cannot catch obfuscated sell blocks or traps activated after launch. This one is also beta and unmeasured. Treat a clean scan as evidence, then run the manual checklist too.
What is the difference between a honeypot and a rug pull? A rug pull drains a token's liquidity pool in one transaction — prevented by locking or burning liquidity. A honeypot blocks holders from selling via the contract itself, and farms buyers continuously. They're different mechanisms with different defenses, which is why a full rug check covers both.
How do I check a Robinhood Chain token's contract manually? Open robinhoodchain.blockscout.com, paste the contract address, and confirm the source is verified. Then scan it for mint, blacklist, fee-setter, and pause functions, check whether ownership is renounced, and read the transfer history for genuine sells from ordinary wallets — not just the deployer.
Are the copycat and vanishing-token scams caught by this checker? Partially. Copycat tickers are beaten by scanning the exact contract address from a trusted source — the checker scans what you paste, so paste carefully. Vanishing tokens rely on contract functions that move holder balances; verification and source review can expose them, but only in verified contracts.
Check before you buy. Lock before you launch. Both sides of that sentence are what keep a market honest.
Explore the rest of our Robinhood Chain guides at the Robinhood Chain hub.
The honeypot checker is beta software provided as-is. Its results are unverified, no warranty is given, and TrustSwap accepts no responsibility for decisions made using it.
TrustSwap is not affiliated with, endorsed by, or sponsored by Robinhood Markets, Inc. Robinhood Chain is a product of Robinhood Markets. All product names are used for identification purposes only.
Lock your liquidity with Team Finance
Get startedTrustSwap is not affiliated with, endorsed by, or partnered with Robinhood Markets, Inc. Robinhood Chain is an independent network; references to it are descriptive only. Nothing here is financial, investment, tax, or legal advice. Token launches carry risk — do your own research.