Robinhood new-pairs agent: eth_subscribe feeds the stream first

Agents that hunt new pools need a steady realtime on-chain feed first. Chinese CT keeps tying Robinhood Chain new pairs / 新池 to agent data feeds—who sees PairCreated first, who ships token / LP / deployer to TG. Paraphrased demand from TheMaran; same window, the Virtuals RH-agent narrative as context. This post stays on the data layer only: subscribe → filter fields → notify, so scripts / agents get a clean new-pair stream.

Open-watch rhythm: Watch Robinhood opens. Volume density: Volume spikes. Whale follow-flow: Whale FOMO watch. This one is the new-pair pipeline—factory events first, then light heuristics.

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 new pairs look like in logs

Tape feel	On-chain signal	Watch
Pool opens	Factory PairCreated (or sibling create-pool log)	token0 / token1 / pair
LP first fill	Early Mint / large Transfer into the pair	LP addr + first liquidity size
Deployer shows	Create-pool tx from; first LP same origin	Store deployer for short-window checks
Short-window heat	Swaps / Transfers in N minutes after open	Buy / sell counts → heat tags

New-pair pipeline = factory event first → extract pair / token / deployer → hang a short buy/sell window. Whale FOMO follows known wallets; this post starts at pool birth.

2. Subscribe → filter → notify (new-pair recipe)

One public WSS: subscribe factory logs → decode fields locally → fake TG / webhook out.

Step A · Subscribe PairCreated (sample topic0)

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

• topics[0] = Uniswap V2-style PairCreated (confirm against factory ABI). Always include factory address.
• After decode: token0 / token1 live in topics or data; store pair → new-pair hit.

Step B · Filter fields (minimum packet for agents / scripts)

Field	Source	Use
pair	PairCreated	Downstream Swap subscribe on that pool
token0 / token1	PairCreated	Display / dedupe key
deployer	Create-pool tx from	Short-window heuristic
txHash / blockNumber	Log metadata	Dedupe + backfill anchor
t0	Hit timestamp	Open short window

Keep the agent JSON lean: { pair, token0, token1, deployer, txHash, t0 }.

Step C · Fake TG / webhook outbound

On hit, POST one payload to a local webhook (or format TG-bot copy): new pair · pair=… · deployer=… · tx=…. The StackBlitz demo uses a fake outbound panel—real secrets stay in local env vars.

3. Preview: new-pairs agent feed (StackBlitz)

Defaults to BlockReq public WSS; subscribe factory → filter pair/token/deployer → fake TG/webhook panel ticks. Code lives in StackBlitz—article embeds the preview only:

Repo: blockreq/blog-demos → examples/robinhood-new-pairs-agent-feed. For keyed: swap trailing public for {API_KEY}.

4. Light heuristics (LP · deployer · short-window buys/sells)

Stabilize the data layer first, then stack a few light tags (demo-tunable):

Tag	Signal	Demo rule
LP first fill	First Mint / large Transfer into pair after open	Record LP size + addr
Same deployer	Create-pool from matches first LP origin	Tag same-deployer
Buy heat	Buy count in N minutes after t0	≥ M → buy-heat
Sell pressure	Sell count in same window	Show beside buy-heat

Flow:

1. PairCreated hit → write minimum packet + open { pair, t0, buys[], sells[] }.
2. In-window, subscribe that pair (or reuse a wider Swap feed and filter) → accumulate buys / sells by direction; dedupe on txHash.
3. Heuristic hit → push tags on the same webhook / board chip.
4. Window expires → archive; new pools open new windows (bucket by pair).

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

5. Summary · Free 3M · RH agent narrative

1. New-pairs agent feed = factory PairCreated → filter minimum packet → TG/webhook notify.
2. Recipe: narrow factory logs + field filter + light LP/deployer/short-window buy-sell tags.
3. Public WSS runs as-is; Free 3M covers short new-pair sessions; long agent boards go keyed.
4. Series: open rhythm · volume density · whale follow-flow · this new-pair pipeline.

When Virtuals-style RH agent narratives heat up, wire the realtime on-chain feed first—subscribe feeds the stream so scripts / agents have something to chew. Next: pin factory addresses → wire webhook to a real bot → persist backfill checkpoints. Public endpoints · Plans & pricing.