Robinhood timed launch: hang eth_subscribe on a known T-0 window

When the launch clock is known, you only need those minutes around T-0. Chinese CT has been buzzing about Robinhood Chain timed launches / 抢开盘—windows like $BOBO at 18:00 UTC, waiting for Pair live, first Swap, and LP in. Demand/context paraphrased from frankli_333 and BOBO_RBH. This post teaches one move: pre-hang eth_subscribe so a known launch window hears PairCreated / first Swap / LP.

Open rhythm: Watch Robinhood opens. Volume density: Volume spikes. Whale follow-flow: Whale FOMO. This one tracks known T-0 · timed launch window.

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 shows up in a launch window

Tape feel	On-chain signal	Watch
Pair lands	Factory PairCreated	token0 / token1 / pair address
First trade	First Swap / Transfer on the new pair	First txHash, side, size
LP in	Mint / add-liquidity Transfer cluster	Liquidity size, provider
Open cluster	Multi-events same blocks around T-0	One alert card packs them

Known clock → set local tStart / tEnd (e.g. 18:00 UTC ± 5 min). In-window pushes become alerts; out-of-window pushes stay as quiet bookkeeping.

2. Timed recipe: public WSS + time-window filter

Connect public WSS, subscribe narrow logs; filter by wall clock / block timestamp locally. For a $BOBO-style 18:00 UTC window, hang subscriptions 1–2 minutes early so PairCreated lands the instant T-0 hits.

Step A · Subscribe PairCreated (sample Factory 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).
• Decode token0 / token1 / pair into the alert card “pair landed”.

Step B · Subscribe Swap / Transfer on the new pair

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

As soon as PairCreated fires, feed pair into the second subscription (or filter by address locally). First in-window Swap → first trade.

Step C · Time-window latch

Action	Demo rule
Open window	now ∈ [tStart, tEnd] (e.g. 18:00 UTC ± 5 min)
Hit	In-window PairCreated / first Swap / LP Mint → push alert card
Archive	now > tEnd → close window, events go to replay bucket

Align wall clock to UTC; block timestamp as a second check. Tune the ±N minutes yourself.

3. Preview: timed launch watch demo (StackBlitz)

Defaults to BlockReq public WSS; fill Factory + T-0 clock, live-tag “pair / first trade / LP”. Code lives in StackBlitz—article embeds the preview only:

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

4. Alert card fields (pair / first trade / liquidity)

1. Pair landed → { pair, token0, token1, factoryTx, ts }.
2. First trade → { pair, txHash, side, amountIn, amountOut, ts }; dedupe on txHash.
3. Liquidity → { pair, lpMintTx, liquidity, provider, ts }; add-liq clusters can stack an “LP in” tag.
4. Open cluster → all three in the same window → one card to webhook / board.

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

5. Summary

1. Timed launch = known T-0 → pre-hang eth_subscribe → hear PairCreated / first Swap / LP in-window.
2. Recipe: Factory + new-pair narrow logs + local time window → three-field alert card.
3. Public WSS runs as-is; Free 3M covers one launch-window session; long boards go keyed.
4. Series: open rhythm · volume density · whale FOMO · this timed window.

Next: pin the T-0 schedule as JSON → wire alert cards to webhooks → persist backfill checkpoints. Public endpoints · Plans & pricing.