BlockReq
Back to all articles

Rpc Tutorials

HARMONIC RHC agent launch listen: Pons / Hookr path

Robinhood Chain agent/token launch path: public WSS eth_subscribe on Pons TokenLaunched / Hookr launchpad / V4 Initialize — editable factory·topic, launch cards out. Register for 3M free requests monthly.

BlockReq EngineeringSeptember 13, 20265 min read

HARMONIC RHC agent launch listen: Pons / Hookr path

HARMONIC / ChillTRD frames the tape as a Robinhood Chain agent-asset path—X + site launch → Pons / Hookr venue → wallet / LP / strategy vault. This post watches the launch heartbeat: Factory TokenLaunched (or Hookr launchpad / V4 Initialize) arrives → decode token / curve / deployer → open card. PONS one-pad converge watches a single pad; here we fold the agent launch path into an editable multi-venue screen.

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

UseEndpoint
Public HTTPShttps://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
Public WSSwss://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
PrivateTrailing public{API_KEY} (keys stay local)

Chain: Robinhood Chain EVM chainId = 0x1237 (4663). Public endpoints · eth_subscribe · Plans · Register.

1. Hook: agent launch path × open card

Tape feelOn-chain signalWatch
Pons curve openFactory TokenLaunchedtoken · curve · deployer · pairToken
Hookr pool-firstLaunchpad open / V4 InitializepoolId · currency0/1 · hooks
Agent asset landsFirst cluster in launch tx windowpad label + launchTx
Sniper tapehit → outboundDedupe = token + launchTx
VenueContract (editable prefills)Role
Pons V2 factory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7eprimary TokenLaunched path
Pons V1 factory0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feBoptional legacy parallel
Hookr launchpad (docs live)0xa043caBE645636899dDe91Cce4693C00a015e660pool-first launches
Uniswap V4 PoolManager0x8366a39CC670B4001A1121B8F6A443A643e40951Initialize layer
WETH0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73quote hint

HARMONIC token / agent vault / LP manager addresses stay off the fixed table until verified on-chain—demo paste fields accept them when known.

2. Event: TokenLaunched → optional Hookr / Initialize

Keep local JSON LAUNCH_FACTORY (multi-address OK) + LAUNCH_TOPIC0 + optional POOL_MANAGER. One RH public WSS: primary Pons V2 TokenLaunched; optional Hookr launchpad + PoolManager Initialize.

Step A · Subscribe Pons V2 TokenLaunched

{
  "jsonrpc": "2.0", "id": 1, "method": "eth_subscribe",
  "params": ["logs", {
    "address": "0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e",
    "topics": ["0x8d4aad4953d0ca700d468f3753aa14432d1b35b43ec6409f051fb6aa43a89607"]
  }]
}
  • topics[0]: TokenLaunched(address,address,address,address,uint256,uint256)
  • topics[1] = token · topics[2] = curve · topics[3] = deployer
  • data: pairToken · launchConfigId · graduationThreshold
  • Write launchState[token], tag pons-v2

Step B · Optional: Hookr launchpad logs

{
  "jsonrpc": "2.0", "id": 2, "method": "eth_subscribe",
  "params": ["logs", {
    "address": "0xa043caBE645636899dDe91Cce4693C00a015e660",
    "topics": ["HOOKR_LAUNCH_TOPIC0"]
  }]
}
  • HOOKR_LAUNCH_TOPIC0: confirm against Hookr launchpad ABI (editable in demo); generation addresses can rotate—paste the live launchpad.
  • Decode token / pool / quote → tag hookr.

Step C · Optional: V4 Initialize (pool-ready layer)

{
  "jsonrpc": "2.0", "id": 3, "method": "eth_subscribe",
  "params": ["logs", {
    "address": "0x8366a39CC670B4001A1121B8F6A443A643e40951",
    "topics": ["0xdd466e674ea557f56295e2d0218a125ea4b4f0f6f3307b95f85e6110838d6438"]
  }]
}

Same-window currency0 / currency1 hitting open launchState → stack pool-ready.

FieldRule
padpons-v2 / pons-v1 / hookr / v4-init
token / curve / deployerTokenLaunched topics
pairToken / thresholddecoded data
poolId / hooksInitialize layer (optional)
readyprimary launch event seen

Step D · Open-card fields

{ chain: "robinhood", pad, token, curve, deployer, pairToken, threshold, poolId?, launchTx, blockNumber, ts }

Dedupe on token + launchTx; demo knobs: factory list + topic0.

3. Browser demo (StackBlitz)

Default RH public WSS; Pons V2 factory / TokenLaunched topic prefilled and editable — optional Hookr + PoolManager — hit Start, stream agent-launch cards. Code lives in StackBlitz — the post only embeds the preview:

Repo: blockreq/blog-demosexamples/harmonic-rhc-agent-launch-listen (Vite+React+viem; open repo root in StackBlitz).

Product page: ZH · EN

WSS  → wss://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
HTTPS→ https://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public
env  → LAUNCH_FACTORY · LAUNCH_TOPIC0 · HOOKR_LAUNCHPAD · HOOKR_LAUNCH_TOPIC0 · POOL_MANAGER · INIT_TOPIC0

Keyed: swap trailing public for {API_KEY}. Quota: blockreq.com register for 3M free requests monthly.

4. Alert rhythm

  1. TokenLaunched arrives → decode token / curve / deployer / pairToken · open the window.
  2. Hookr / Initialize (optional) → stack pad / poolId on same token.
  3. OutboundHARMONIC RHC · pad=pons-v2 · token=… · curve=… · deployer=… · launchTx=… · blk=….
  4. Dedupe → one push per token + launchTx.

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. Grain: HARMONIC RHC agent open = Pons / Hookr launch-path listen.
  2. Recipe: TokenLaunched topic0 + editable venue list → open card; optional Hookr / V4 Initialize.
  3. Runnable: browser on BlockReq RH public WSS; demos1 paths above.
  4. Start: Public endpoints + blockreq.com register for 3M free requests monthly.

Next: widen the venue table → webhook → stack on-screen with PONS one-pad / any-quote launch. Docs · Pricing · Register.