Robinhood stock-pairs launch: eth_subscribe for Bags Stock Pairs

Beyond plain meme pools—the new token lands paired with a tokenized stock. Chinese CT has been buzzing about Bags Stock Pairs / 币股配对: one side community token, the other a Robinhood Stock Token (AAPL / TSLA / NVDA-class). Context paraphrased from finnbags and diaomao2023. This post teaches one move: hang eth_subscribe on Factory + a stock-token address table, and hear PairCreated / first LP / paired-asset address.

Timed T-0 countdown: Timed launch watch. Open rhythm: Watch Robinhood opens. This one tracks the stock-paired mechanism—which stock token the new pool pairs with.

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 stock pair shows up on-chain

Tape feel	On-chain signal	Watch
Paired pool lands	Factory PairCreated	token0 / token1 / pair; one side ∈ stock-token table
Paired-asset address	Stock side decoded from PairCreated	Remember symbol / stockTokenAddr
First LP	First Mint / add-liq Transfer cluster on new pair	Liquidity size, provider
Paired open cluster	PairCreated + first LP same window	One alert card packs them

Stock Pairs = your local Stock Token address table (lowercase, deduped) + Factory narrow logs. Tag stock-pair only when one side hits the stock table.

2. Stock table + eth_subscribe (pairs recipe)

Keep a stock-token watchlist locally (contracts for AAPL / TSLA / NVDA, etc.). One public WSS, subscribe Factory PairCreated; on each push, table-lookup token0 / token1.

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: either side in stock table → stock-pair hit; remember the paired-asset address.

Step B · Subscribe Mint / Transfer on the new pair (first LP)

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

As soon as PairCreated fires, feed pair into the second subscription. Common V2 Mint topic0 shown above (confirm against pool ABI). First in-window add-liq cluster → first LP.

Step C · Pair latch

Action	Demo rule
Hit pair	PairCreated and token0 or token1 ∈ stock table
Remember asset	pairedAsset = stock-side addr; memeSide = other side
First LP	First Mint / add-liq on new pair → stack “LP in”
Push card	Pair hit + first LP → one alert card

Timed-launch uses a T-0 time window; this post uses a stock address table—different mechanism, complementary recipes.

3. Preview: stock-pairs launch demo (StackBlitz)

Defaults to BlockReq public WSS; paste stock-token table + Factory, live-tag “pair landed / paired asset / first LP”. Code lives in StackBlitz—article embeds the preview only:

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

4. Alert card fields (pair / paired asset / first LP)

1. Pair landed → { pair, token0, token1, factoryTx, ts }.
2. Paired asset → { pairedAsset, symbolHint, memeSide, ts }; stock-table side wins.
3. First LP → { pair, lpMintTx, liquidity, provider, ts }; dedupe on txHash.
4. Paired open cluster → all three → one card to webhook / board.

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

5. Summary

1. Stock-pairs launch = PairCreated with one side ∈ Stock Token table → remember paired asset → hear first LP.
2. Recipe: Factory narrow logs + local stock table lookup + new-pair Mint → three-field alert card.
3. Public WSS runs as-is; Free 3M covers a short pairs-launch session; long boards go keyed.
4. Series: timed T-0 countdown · open rhythm · this stock-paired mechanism.

Next: pin the stock-token address table as JSON → wire alert cards to webhooks → persist backfill checkpoints. Public endpoints · Plans & pricing.