Robinhood bridge rotation: eth_subscribe for cross-chain netflow

Want the right tool for the job. Capital rotation often shows on bridges first—how much in, how much out, whether 5/15/60-minute netflow thickens into a move. Bridge-flow numbers paraphrased from the thread around DefiIgnas; optional tokenized-stock heat from Cointelegraph. This post does one job: hang bridge in/out logs on eth_subscribe, roll netflow by window, and tag rotation.

Volume density: Volume spikes. Whale follow-flow: Whale FOMO. This one tracks bridge netflow / rotation—a different lane from pool density or wallet follow tables.

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. Why rotation shows on bridges first

Tape feel	On-chain signal	Watch
Funds enter bridge	Deposit / Lock / Message-style log: amount into bridge	Bucket in + token
Funds leave bridge	Withdraw / Unlock / Release-style log	Bucket out + token
Short-window netflow	Same bridge + token: sum(in) − sum(out)	5 / 15 / 60m windows
Rotation lifts	Netflow steep vs baseline, or both sides thicken	Tag bridge-rotation

Bridges = your local bridge watchlist. Signal = in/out logs on known bridge contracts, then netflow—separate from pool Swap density and leader-wallet follow flow.

2. What bridge in/out logs look like

Keep a bridge table locally: { bridge, token?, directionTopic } (lowercase, deduped). One public WSS, narrow logs; on each push, decode and bucket by direction.

Step A · Subscribe bridge logs (with address)

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

• Always include address (the bridge). With ABI, narrow topics[0] further (or run Deposit / Withdraw as two subs).
• After decode, map event name or topic0 → in / out; normalize amount by token decimals; dedupe on txHash.

Step B · Direction map (demo)

Direction	Event feel	Bucket
in	Deposit / Lock / BridgeIn	inBuckets[window].push(amount)
out	Withdraw / Unlock / BridgeOut	outBuckets[window].push(amount)
netflow	—	net = sum(in) − sum(out)

Pin real topic0 hashes from the bridge ABI in production; demo can map by event name.

Step C · Three rolling windows

Window	Demo use
5m	Short pulse: netflow just lifting
15m	Confirm: pulse holds
60m	Baseline: slope vs short windows

Slide each log into all three windows by timestamp; drop samples past the edge. Netflow feeds the threshold layer next.

3. Preview: bridge rotation demo (StackBlitz)

Defaults to BlockReq public WSS; paste a bridge address, subscribe, and live-refresh 5/15/60m netflow. Code lives in StackBlitz—article embeds the preview only:

Repo: blockreq/blog-demos → examples/robinhood-bridge-rotation-watch. For keyed: swap trailing public for {API_KEY}.

4. Alert thresholds (netflow / rotation)

1. Baseline → use 60m net or a near-N window mean as background.
2. Short lift → net_5m vs baseline ≥ multiple / absolute floor → bridge-netflow-lift.
3. Confirm → net_15m same direction holds → bridge-rotation-confirm (webhook / board chip).
4. Both sides thicken → same-window in and out both up vs baseline → bridge-activity-thick (rotation in progress).

Tune yourself (demo often: 5m net ≥ baseline × 2 and above a floor). Tags = interpretation: JSON → dashboard / alert copy.

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

5. Summary

1. Bridge rotation = bridge in/out logs → 5/15/60m netflow → threshold tags.
2. Recipe: narrow logs (bridge address) + direction buckets + three-window netflow → lift / confirm / thicken.
3. Public WSS runs as-is; Free 3M covers short bridge sessions; long boards go keyed.
4. Series: volume density · whale follow-flow · this bridge-netflow post. When tokenized-stock heat rises, the same bridge windows often show fund skew first.

Next: pin bridge watchlist as JSON → wire netflow tags to webhooks → persist backfill checkpoints. Public endpoints · Plans & pricing.