Skip to main content
Lasso tested newHeads subscription recovery during provider replacement on a surviving downstream WebSocket connection. This is a controlled continuity test, not a guarantee across client disconnections, application-node loss, or exhausted recovery bounds. Applications should keep checkpoints and reconcile after reconnecting. See subscription recovery limits.

​
Test and result

On August 22, 2026, a pinned Lasso implementation ran a 30-minute in-process soak. Fifty downstream clients shared one upstream newHeads subscription. The harness forced a provider replacement every 15 seconds and skipped three live blocks per replacement so HTTP replay had to restore the gap. It recorded 119 replacements, zero downstream gaps, and zero replay-created duplicates. The coordinator count stayed at one. Subscription state drained after the last client left, within the test’s 95-second teardown limit.
This is a Lasso-run gate against implementation commit 89ad1a09ad88a1cf86a1dbc8ac5de6feb526b5f3. Its Cloud harness is not part of the public RPC Core release, so this result is reported evidence, not a command you can reproduce from the public repository. It measures bounded replacement within one profile and one running process. It does not measure a general hosted capacity, SLA, or exactly-once delivery guarantee.