How to spot a rug pull

2026-07-15 · 5 min read · Splitshot Team

A rug pull is a token designed so that the people who created it can take the money out and the people who bought it cannot. That is the whole category. The methods vary, but every rug reduces to one of a few mechanical tricks, and each trick leaves fingerprints you can check before you buy. This guide covers the classic patterns, then the specific checks that work on Robinhood Chain.

None of this requires reading Solidity. It requires a block explorer, the token's price page, and about five minutes of skepticism.

Pattern 1: liquidity that can walk away

The most common rug is the simplest. The deployer creates a pool, seeds it with liquidity, waits for buyers to trade real ETH or stablecoins into it, then withdraws the entire pool. The chart goes vertical, then goes to zero in one transaction. Nothing about this is a hack; removing your own liquidity is a normal, permitted operation.

What you are checking for is whether the liquidity is committed or merely present:

On Uniswap v3, which is the pool standard on Robinhood Chain, liquidity positions are NFTs. You can see on the explorer which address holds the position for a token's main pool and whether that address is the deployer, a locker, or a burn address.

Pattern 2: mint functions and owner privileges

The second family of rugs lives inside the token contract itself. An ERC-20 is just code, and the code can include an owner-only mint function with no cap. A deployer holding that power does not need to pull liquidity; they can mint an arbitrary number of new tokens and sell them into the pool, diluting every holder to nothing.

Mint is the famous one, but any of these owner privileges can serve the same purpose:

The check: open the contract on the explorer and look at the verified source. If the source is not verified at all, you cannot inspect any of this, and that alone is a reason to pass. If it is verified, search the source for mint, owner, blacklist, and fee. You do not need to understand every line; you need to see whether the deployer retained levers over your balance. Contracts that renounce ownership give those levers up, though renouncing also removes the ability to fix anything, so it is a signal rather than a guarantee of quality.

Pattern 3: honeypots, or tokens you can buy but not sell

A honeypot inverts the trap. Buys work perfectly, the chart climbs, and every sell reverts or gets taxed into dust. Common implementations include a sell tax set near 100 percent, a max-sell limit of effectively zero, transfer functions that only whitelisted addresses can complete, and logic that behaves differently for the deployer than for everyone else.

Honeypots are hard to spot from the chart, because the chart shows buys and the buys are real. Two practical defenses:

  1. Look for two-way trade history. On the explorer, check the pool's recent transactions for successful sells from ordinary wallets, not just buys. A token with hundreds of buys and no third-party sells is telling you something.
  2. Test with dust. If you still want in, buy a tiny amount and immediately try to sell it back. Losing a few cents to fees is the cheapest audit you will ever run. Size up only after the round trip works.

Pattern 4: copycat names

The laziest rug does not need a clever contract at all. It needs the same name and logo as a token people already want. Token names and symbols are freely copyable by anyone deploying a contract; nothing on any EVM chain prevents a second, third, or fiftieth token called the same thing. The contract address is the only identifier that cannot be copied.

Robinhood Chain has plenty of this, including tokens that impersonate well-known brands. Splitshot flags impersonating tokens, and flagged tokens never appear on its indexable pages, but a flag system is a filter, not a promise. The habit that actually protects you is refusing to trust names at all: always trade by address.

Checking a token on Robinhood Chain, specifically

The chain's explorer is Blockscout, at robinhoodchain.blockscout.com. The routine:

  1. Get the contract address from the project's own official channel, not from a search result, a Telegram DM, or someone's reply.
  2. Paste the address into Blockscout. Confirm the contract source is verified and skim it for the owner privileges described above.
  3. Open the holders tab. If a handful of wallets outside the pool hold most of the supply, they can end the token whenever they decide to sell.
  4. Find the token's main pool and check who holds the liquidity position, and whether it is locked or burned.
  5. Compare the address against the one on the token's Splitshot price page. The price page shows the contract address, the measured volume, and the pool depth behind the price. Thin liquidity is not a rug by itself, but it is the environment rugs prefer.

The pre-buy checklist

Compressed to what you can run in five minutes:

  1. Address obtained from an official source, and it matches the price page
  2. Contract source verified on Blockscout
  3. No uncapped mint, changeable tax, or blacklist in the source, or ownership renounced
  4. Liquidity locked or burned, with a lock long enough to matter
  5. Holder distribution not dominated by a few non-pool wallets
  6. Successful sells from ordinary wallets visible in recent history
  7. A dust-sized round trip, buy then sell, completes

No checklist catches everything. A patient scammer can lock liquidity, renounce ownership, and still walk away by dumping a large pre-mined allocation slowly. What the checklist does is remove the cheap, common traps, which is most of them. The rest is position sizing: on a fresh token that passed every check, the honest maximum stake is still an amount you can lose without flinching.

If a token clears your checks and you decide to trade it, the swap walkthrough covers execution, and the live price pages will show you the measured numbers as they change.

Ready to trade on Robinhood Chain?

Open the swap