← blog · 2026-09-11 · 2 min read

Copy-trading on fomo.family: when you become exit liquidity

How social copy-trading on Robinhood Chain turns late followers into exit liquidity — synced buys, empty pools, crowding, and what the hoodwatch.dev tape flags.

fomo.family makes it easy to follow ranked traders and copy a memecoin buy in one tap. That speed is also why coordinated launches work: the follower wave is visible, and late followers become the exit liquidity for wallets that were first.

hoodwatch.dev does not replace the app. It reads the on-chain side of those fills — who bought, whether the token can be sold, whether the pool has quote-side money — and puts that on a live tape. How the product is built: What is hoodwatch?. How a fomo trade settles: fomo.family explained.

Failure modes that are not honeypots

A honeypot is a token you can buy and cannot sell. That is one failure mode; How honeypots work on Robinhood Chain covers how we test for it.

Most losses on this market come from tokens that pass that check. The pool is sellable; there is just nobody left to sell to, because the buying you copied was staged. Three patterns:

Rules and tells: Synced buys, empty pools and copycat tickers. Quote-side vs headline liquidity: Robinhood Chain memecoins.

Crowding is a clock

The weekly export buckets how many tracked buyers appear in the first 30 minutes after the first tracked buy. More tracked wallets in that window has, in the weekly cut, gone with higher median peaks — and the 30-day backtest says that late after the crowd is where median outcomes go negative. You are then paying the exit of wallets that were already in.

Read both, do not mix them: What 30 days of fomo tape data say about following the crowd and the public exports / week 2026-W37.

Early vs late, in practice

hoodwatch.dev marks FIRST BUY for ranked or alpha wallets and shows run-up since that buy so “late” is visible. It does not invent a weekly hit rate on this page; cite the export or the weekly post.

Checklist before mirroring a notification

  1. Can it be sold? Honeypot / transfer-blocked / pool-blocks-sells / template flags on the tape.
  2. Is the pool real? Quote-side liquidity, not the headline number.
  3. Who is buying, and how? One ranked first print is a different object from three synced first buys.
  4. How late? Run-up since the first tracked buy; 30-minute crowding bucket.
  5. Deployer / template history? Prior honeypots or rugs on the same launcher.

If the question is only “who bought this launch on fomo, and can it be sold?”, that is hoodwatch.dev — not hoodwatch.io or the Rust auditor.

hoodwatch.dev is unofficial and not affiliated with fomo.family or Robinhood. Nothing here is financial advice.


hoodwatch.dev is unofficial and read-only, not affiliated with fomo.family or Robinhood. Nothing here is financial advice. Open the live tape.

fomo.family on Solana: how hoodwatch attributes Solana trades to fomo traders

fomo.family traders also trade on Solana, through pump.fun, PumpSwap, Jupiter and Meteora. Their trading wallets are not the ones on their profiles and most swaps are relayed. Here is how hoodwatch maps and reads them, and what the Solana tape shows.

Who got there first: fomo.family first-buy leaders, week 2026-W37

First tracked buyers on the hoodwatch.dev tape for 2026-W37: DuckSoldier 78 first buys / 16 ≥3x, skoqv MARIO 284.3x, 0xangeryy UNIPCS 84.4x, cryptochi3f_ par 120.2x.

hoodwatch.dev vs hoodwatch.io (and the Rust auditor): which is which

Three different products share the Hoodwatch name. This page explains hoodwatch.dev (fomo tape), hoodwatch.io (whale intel), and the aetherBytes Rust auditor.

hoodwatch.dev · smart-wallet flow on Robinhood Chain and Solana · not financial advice