RH V4 direct-open sniper tool: catch one-tx pools

In the PAR / Fox Brokers narrative, RH ships another one-tx direct-open path: token + Uniswap V4 pool land in the same window, tradeable as soon as the pool initializes. Relative to PONS-style bonding-curve pads (progress / graduate), this post listens to PoolManager Initialize / pool-create—the direct-open heartbeat.

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. Hook: another one-tx open-pool path

Tape feel	On-chain signal	Listen focus
Direct open	Same tx: deploy + Initialize + add liquidity	Multi-log cluster on one txHash
Tradeable on init	Swaps available in the same window after Initialize	Open card lands complete
Vs curve pads	Hear pool land; skip bonding progress	topic = Initialize
Hear first	New pool → token / fee outbound	First in-window cluster is enough

Curve pads watch a progress bar; V4 direct open watches the pool heartbeat—once Initialize fires, the book is live.

2. Event model: PoolManager Initialize

One public WSS: subscribe PoolManager Initialize; optionally stack deploy / ModifyLiquidity logs on the same tx and tag “direct open.”

Step A · Subscribe Initialize (direct-open heartbeat)

{
  "jsonrpc": "2.0", "id": 1, "method": "eth_subscribe",
  "params": ["logs", {
    "address": "${POOL_MANAGER}",
    "topics": ["0xdd466e674ea557f56295e2d0218a125ea4b4f0f6f3307b95f85e6110838d6438"]
  }]
}

• Keep POOL_MANAGER in env (swap the live RH deployment address when ready).
• topics[0] = Uniswap V4 Initialize(bytes32,address,address,uint24,int24,address,uint160,int24).
• Decode currency0 / currency1 / fee / hooks / sqrtPriceX96 → write poolId and token candidates.

Step B · Same-tx cluster (optional stack)

Role	Use	Stack
Initialize	Pool lands	Primary subscribe
Token deploy / Transfer	CA candidates	Cluster on txHash
ModifyLiquidity	First liquidity cluster	Same window → firstBlock

Step C · Open-card fields

{ path: "V4-direct", poolId, currency0, currency1, fee, hooks, factoryTx, blockNumber, earlySwap?, ts }

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

3. Browser + BlockReq RH public WSS

In the browser, connect RH public WSS, fill POOL_MANAGER + Initialize topic0, hit Start, and stream direct-open cards. demos1 path (later ship as “V4 direct-open radar”):

:::pages-demo https://blockreq.com/demos1/rh-uniswap-v4-direct-launch-listen/en/ title: RH Uniswap V4 direct-launch listen height: 520 :::

Path hint: /demos1/rh-uniswap-v4-direct-launch-listen/zh/ · /demos1/rh-uniswap-v4-direct-launch-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. Alert: new pool → token / pool / fee; optional newHeads

1. New-pool card → { poolId, tokenA, tokenB, fee, hooks, txHash, blockNumber }.
2. Optional early density → also subscribe newHeads; count Swap hits for the fresh poolId over the first M seconds / N blocks.
3. Push rhythm → outbound on Initialize; paint early Swap density as a second chip.

{
  "jsonrpc": "2.0", "id": 2, "method": "eth_subscribe",
  "params": ["newHeads"]
}

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

5. Summary + CTA

1. V4 direct open = PoolManager Initialize / pool-land heartbeat (relative to curve-progress paths).
2. Recipe: POOL_MANAGER + Initialize topic + same-tx cluster → open card; optional newHeads for early Swap density.
3. Runnable: browser on BlockReq RH public WSS; demos1 can later ship the “V4 direct-open radar.”
4. Start: Public endpoints + blockreq.com register for 3M free requests monthly.

Next: pin RH POOL_MANAGER / topic list → wire open cards to webhooks → run side-by-side with the PONS one-pad listen recipe. Docs · Pricing · Register.