When PONS dominates: converge open-listen onto one launchpad

When volume concentrates on PONS, open signals densify with it—narrow eth_subscribe to one launchpad Factory + key topics, hang BlockReq public WSS in the browser, and hear open cards tighter and faster. This post teaches that single convergence recipe.

Run on the public endpoint · blockreq.com register for 3M free requests monthly.

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: Robinhood Chain EVM chainId = 0x1237 (4663). Public endpoints · eth_subscribe · Plans · Register.

1. Why one pad: volume concentration → denser signal

Tape feel	Listen strategy	You get
PONS dominates	Single Factory address	Opens concentrate on one subscription
Volume concentrates	Key-topic narrow listen	Denser pushes, fuller fields
Hear first	Open card goes outbound early	First in-window cluster is enough
Faster demo	One browser WSS	Runnable in minutes

Full-chain multi-Factory scans cover wide and push sparse; one-pad convergence packs more open hits per minute—better alert rhythm for short tape sessions. Stock-pair ID can stack on the same Factory subscribe: Stock-pair meme launches.

2. Subscribe PONS factory / key event topics

Keep PONS_FACTORY in env (swap the live on-chain address when ready). One public WSS; subscribe Factory open / PairCreated-class topics.

Step A · Subscribe PONS Factory open logs

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

• address = process.env.PONS_FACTORY (placeholder → live Factory).
• topics[0]: sample V2-style PairCreated; if PONS ships its own Launch / CreatePair topic, swap that one item—subscribe shape stays the same.
• Decode token0 / token1 / pair (or ABI equivalents) → write launchState.

Step B · Key topic checklist (demo-configurable)

Topic role	Use	Stack
PairCreated / Launch	Open lands	Primary subscribe
Mint / add-liq	First liquidity cluster	Feed pair into second subscribe
Swap	First trade / early volume	Same window → firstBlock

Step C · Open-card fields

{ pad: "PONS", pair, token0, token1, factoryTx, blockNumber, earlyVolume?, ts }

Dedupe on txHash / pair; merge repeat pushes for the same pair inside a short sliding window.

3. Browser + BlockReq public endpoint + register for 3M free requests monthly

In the browser, connect RH public WSS, fill PONS_FACTORY + topic0, hit Start, and stream one-pad open cards. Live demos1:

Path hint: /demos1/pons-launchpad-listen/zh/ · /demos1/pons-launchpad-listen/en/. For keyed: swap trailing public for {API_KEY}.

Quota to start: blockreq.com register for 3M free requests monthly (public endpoint connects as-is).

4. vs full-chain scan: denser signal, faster demo

Dimension	Full-chain multi-Factory	PONS one-pad
Subscribe surface	Many addresses / topics	One Factory + key topics
Push density	Events spread thin	Volume concentration → denser open clusters
Field completeness	Needs second-pass aggregation	Open-card fields land in one pass
Demo pace	Cold start slower	One browser WSS runs in minutes
Stack plays	Wide net	Can stack stock-token table / quote whitelist

Recipe pick: when volume already concentrates on PONS, prefer one-pad convergence—same public endpoint, tighter listen, faster alerts.

On disconnect: reconnect and re-subscribe; gap-fill with HTTPS eth_getLogs on the same Factory. POST → https://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public.

5. Summary + CTA

1. One-pad converge = PONS Factory + key topics → denser open signal.
2. Recipe: PONS_FACTORY env + narrow logs + first Mint/Swap stack → open card.
3. Runnable: browser on BlockReq RH public WSS; demos1 is live on public WSS.
4. Start: Public endpoints + blockreq.com register for 3M free requests monthly.

Next: pin PONS_FACTORY / topic list → wire open cards to webhooks → stack with the stock-pair meme address table. Docs · Pricing · Register.