Watch Robinhood KOL wallets: eth_subscribe Transfer watchlist

Tool lists are getting bookmarked hard—the thread around ProMint_X (~541 bookmarks) stacks Robinhood Chain gear, but peel it down and the everyday core is often just subscribe a batch of KOL / smart-money wallets. Nearby timelines also nod travladd-style copytrade / FOMO talk; this post does not guess entries. One job only: hang a multi-address watchlist on eth_subscribe Transfer logs—who moved, which token, whether several watchlist names spike the same window.

Whale FOMO counts follow-buys after a leader hit: Whale FOMO. Position watchtower tracks your own holding-period state machine: Position watchtower. This one is multi-address KOL / smart-money Transfer watch.

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. What Transfer-to-watchlist looks like

Tape feel	On-chain signal	Watch
KOL moves	Transfer: from or to ∈ watchlist	Label + token + side
Smart-money rotate	Same addr, several Transfers in/out quickly	Group by token; mark rotate spike
Multi-addr same window	≥2 watchlist addrs touch same token	Dedup, stack follow-spike
Dust noise	Tiny value / duplicate pushes same tx	Amount floor + txHash dedupe

Watchlist = your local KOL / smart-money table (lowercase, deduped, optional nicknames). Signal = Transfer involving known addresses—no FOMO follow-window yet; that lives in the whale post.

2. Multi-address + eth_subscribe (KOL watch recipe)

Keep a watchlist locally: [{ addr, label }]. One public WSS, narrow Transfer logs; on each push, table-lookup from / to.

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) whenever you can narrow.
• Decode: topics[1] = from, topics[2] = to (32-byte right-aligned). Either side in watchlist → KOL hit.

Step B · Multi-address dedupe + follow spike

Action	Demo rule
Enqueue hit	{ label, addr, token, side, value, txHash, ts }
Dedupe	Same txHash + addr + token → keep one
Follow-spike	Within N minutes, ≥ K distinct watchlist addrs on same token → follow-spike

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

3. Preview: multi-address KOL watch demo (StackBlitz)

Defaults to BlockReq public WSS; paste a multi-address list, live-tag KOL hits / dedupe / follow-spike. Code lives in StackBlitz—article embeds the preview only:

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

4. Fields + a small noise filter

Suggested push fields:

Field	Meaning
label / addr	Watchlist nickname and address
token / side	Contract; in / out relative to watched addr
value	Raw amount (format with decimals later)
txHash / blockNumber	Dedupe + backfill anchors
tags	kol-hit · rotate · follow-spike

Small noise filter (demo):

1. Dust → drop if value < V_min (after decimals).
2. Same-tx dupes → Set key txHash|addr|token|side.
3. Self-shuffle → from / to both on watchlist with tiny value → tag noise or skip push.

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

5. Free 3M + summary

1. KOL wallet watch = multi-address watchlist hits on Transfer → dedupe → optional follow-spike tags.
2. Unlike whale FOMO, you first watch who is moving; unlike position watchtower, you watch others' smart-money table, not your own holding state.
3. Public WSS runs as-is; Free 3M covers short KOL sessions; long boards go keyed.
4. Series: Whale FOMO · Position watchtower · this multi-address Transfer watch.

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