River Room Contract C4ckLEzJ4HE8W861ZSyopScAPX4hwBkyKeAxUof1QMXs — Update Propagation Report
Updates are propagating well. Here's the summary:
Activity (recent telemetry window):
- 42 update_request events
- 14 update_success events (all completed, no stuck operations)
- 200 update_broadcast_received / 171 update_broadcast_applied
- Zero timeouts, zero failures, zero errors for this contract
Propagation:
- 20 unique peers successfully applying updates recently
- 126 unique peers with subscription activity
- Updates propagating in real-time — the trace shows a healthy broadcast tree with multi-hop fan-out
Broadcast delivery stats (recent summaries):
- send_failed: 0 across all recent deliveries
- resolve_failed: 0 (both interest and proximity)
- Typical fan-out: 3-5 targets per hop
- skipped_summary_match occasionally fires (expected dedup behavior)
Key active peers in the subscription tree:
- 2NrGugfwLooZ, QSA6BHzv4Cum, RSiPXQnHRTLb — frequently originating updates (likely gateway nodes or active users)
- i4QWRJcwgtBx — consistently receiving and confirming update_success
- Good spread across sz9Pa1W, ZY25EXP, zdZotzQ, 36kRuDw, 41XBsJ7, etc.
Verdict: The official River room contract is healthy — updates are propagating through the subscription tree with zero failures, multi-peer fan-out, and sub-second delivery latencies. The 0.1.139 release looks clean from a propagation standpoint.