Watch Robinhood whale wallets: eth_subscribe for FOMO follow flow

Want the right tool for the job. Chinese CT timelines keep asking for Robinhood Chain whale / “车头” watch, FOMO, and hot-flow alerts—who moves first, who piles in, whether follow-buys thicken in a few minutes. Paraphrased demand from the thread around 0xKevin00. This post does one job: hang a leader-wallet watchlist on eth_subscribe Transfer / Swap logs, count short-window follow-buys, and tag FOMO.

Open-watch rhythm: Watch Robinhood opens. Volume density: Volume spikes. This one tracks leader → follow flow.

Use	Endpoint
Public HTTPS	https://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
Public WSS	wss://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
Private	Trailing public → {API_KEY} (keys stay local)

Chain: EVM chainId = 0x1237 (4663). Free 3M Requests / 30 days · Public endpoints · eth_subscribe · Pricing.

1. How a whale signal shows up on-chain

Tape feel	On-chain signal	Watch
Leader enters	Transfer / Swap: from or party ∈ watchlist	Hit → open FOMO window
Leader rotates	Same addr, several Transfers in/out quickly	Remember token / pool
Follow-buy flow	Other addrs buy same token / pool in-window	Count ≥ M → FOMO
Hot handoff	Multiple leaders touch same token in-window	Dedup leaders, stack tag

Leaders = your local watchlist. Signal = Transfer / Swap involving known addresses, then count short-window followers.

2. Watchlist + eth_subscribe (whale recipe)

Keep a lowercase, deduped watchlist locally. One public WSS, narrow logs; on each push, table-lookup from / to (or Swap parties).

Step A · Subscribe Transfer (sample topic0)

{
  "jsonrpc": "2.0", "id": 1, "method": "eth_subscribe",
  "params": ["logs", {
    "topics": ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
  }]
}

• topics[0] = ERC-20 Transfer. Add address (token / pool) whenever you can narrow.
• After decode: topics[1] = from, topics[2] = to (32-byte right-aligned). Either side in watchlist → leader hit.

Step B · Subscribe Swap (when you have pool ABI)

{
  "jsonrpc": "2.0", "id": 2, "method": "eth_subscribe",
  "params": ["logs", {
    "address": "0xYourPoolAddress",
    "topics": ["0xd78ad95fa46c994b6551d0da85fc275fe613ce37657fb8d5e3d130840159d822"]
  }]
}

Common Uniswap V2-style Swap topic0 shown above (confirm against pool ABI). Leader as sender / to counts as a hit; remember pool / token.

Step C · Open a short window on hit

Action	Demo rule
Open window	Leader hit → store token / pool + t0
Follow-buy	Within N minutes after t0, non-watchlist buys on same target
Tag	Follow count ≥ M → FOMO; multi-leader same window → hot-handoff

Tune N / M yourself (demo often N=3, M=5). Tags = interpretation: JSON → dashboard chips / alert copy.

3. Preview: whale watchlist demo (StackBlitz)

Defaults to BlockReq public WSS; paste a leader list, live-tag leader hits / FOMO / hot-handoff. Code lives in StackBlitz—article embeds the preview only:

Repo: blockreq/blog-demos → examples/robinhood-whale-fomo. For keyed: swap trailing public for {API_KEY}.

4. FOMO rule (N minutes / M follow-buys)

1. Leader hit → open { tokenOrPool, t0, leaders, follows[] }.
2. In-window, each non-leader buy: follows.push({ addr, txHash, ts }); dedupe on txHash.
3. follows.length ≥ M and now - t0 ≤ N min → tag FOMO; push webhook / board chip.
4. Window expires → archive; same leader moving again can open a new window (bucket by token).

Disconnects: reconnect → re-subscribe; gap-fill with HTTPS eth_getLogs in block segments, replay the same watchlist / FOMO rules. POST → https://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public.

5. Summary

1. Whale / FOMO watch = watchlist hits on Transfer/Swap → count short-window follow-buys.
2. Recipe: narrow logs + local table lookup + N minutes / M follows → FOMO / hot-handoff.
3. Public WSS runs as-is; Free 3M covers short whale sessions; long boards go keyed.
4. Series: open rhythm · volume density · this follow-flow post.

Next: pin watchlist as JSON → wire FOMO tags to webhooks → persist backfill checkpoints. Public endpoints · Plans & pricing.