Robinhood gas heat radar: eth_subscribe for chain-wide launch heat

Heat shows up in gas first. Chinese CT has been watching Robinhood Chain revenue and activity—only1mrwhite highlighted about $2.61M / 24h revenue; people also ask whether the chain “runs hot” before a launch window. This post does one job: hang chain-wide baseFee / gasUsed heat on eth_subscribe newHeads, roll 5/15-minute heat windows, and hint an open window on spikes.

Volume = pool density: Volume spikes. Open rhythm: Watch Robinhood opens. Whale follow: Whale FOMO. This one tracks chain-wide heat → launch-window signal, not a single pool.

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. Heat is written in gas first

Tape feel	On-chain signal	Watch
Chain warms up	newHeads: rising baseFeePerGas	Slope vs 5/15m baseline
Blocks fill up	Higher gasUsed / gasLimit share	Sliding utilization mean
Short-window accel	Δ of baseFee / util across recent heads	Steep slope → heat spike
Open-window hint	Heat spike near a launch window	Route to open-watch / volume

Vs volume-watch: that post tracks pool Transfer/Swap density; this radar tracks chain-wide baseFee + gasUsed heat as a launch-window lead signal—feel the chain warm up, then choose which narrow subscribe to open.

2. Metrics: baseFee · gasUsed share · short-window slope

One public WSS, subscribe newHeads only; roll two local windows (demo often 5m / 15m).

Step A · Subscribe newHeads

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

From each push: baseFeePerGas, gasUsed, gasLimit, timestamp, number.

Step B · Compute heat locally

Metric	Demo math	Use
baseFee heat	Current baseFee vs 5m / 15m mean	Fee lift = contention
Utilization	Sliding mean of gasUsed / gasLimit	How full blocks are
Short-window slope	Δ of baseFee / util over last N heads	Steep → heat spike

Step C · Tag (demo thresholds)

Tag	Simple rule
Heat lift	5m baseFee > 15m mean
Heat spike	5m baseFee > 15m × 1.2 and util > 0.7
Open-window hint	Heat spike near a known local launch window

Tune thresholds yourself. Tags = interpretation: JSON → dashboard chips / alert copy.

3. Preview: newHeads → 5/15m heat (StackBlitz)

Defaults to BlockReq public WSS; live 5/15-minute heat, spike highlight. Code lives in StackBlitz—article embeds the preview only:

Repo: blockreq/blog-demos → examples/robinhood-gas-heat-radar. For keyed: swap trailing public for {API_KEY}.

4. Alert: heat spike → open-window hint

1. Heat spike → push { t0, baseFee, util, slope5m, slope15m }.
2. Open-window hint → link open-watch (rhythm) or volume density (pool logs).
3. Compose → radar shouts “chain is hot”; then narrow pool subscribe / open-watch—less idle spinning.
4. Gap-fill → reconnect → re-subscribe; backfill heads over HTTPS:

{"jsonrpc":"2.0","id":2,"method":"eth_getBlockByNumber","params":["0xBLOCK", false]}

POST → https://robinhood-mainnet-rpc.blockreq.com/v1/rpc/public. Replay the same 5/15m rules; dedupe on number.

5. Summary

1. Gas heat radar = chain-wide baseFee + gasUsed share + short-window slope; launch-window lead signal.
2. Recipe: newHeads + 5/15m windows → heat spike → open-window hint.
3. Differentiates from volume-watch: pool density vs chain gas heat; pairs with open-watch / whale FOMO.
4. Public WSS runs as-is; Free 3M covers short heat sessions; long boards go keyed.

Next: pin thresholds as JSON → wire heat spikes to webhooks → persist backfill checkpoints. Public endpoints · Plans & pricing.