Skip to content

Build a multi-provider WebSocket subscription layer #1721

Description

@bmuddha

Goal

Provide a multi-provider WebSocket subscription layer with bounded connection pools, balanced admission, and explicit subscription-loss notifications.

Why

Account synchronization needs to absorb growing subscription demand without exposing connection management to callers. Reconnecting a socket must not imply that its previous subscriptions remain valid.

Scope

  • Support multiple providers with configurable maximum connections and subscriptions per connection. Route each remote account to one connection; overlapping requests should share an acknowledged subscription until its last reference is released.
  • Admit new subscriptions round-robin across healthy connections with available capacity. Do not move existing subscriptions solely for balancing.
  • Grow pools preemptively in batches at 75% of allocated capacity, within provider limits. A full or disconnected provider should not prevent healthy providers from growing.
  • Report acknowledgement, account updates, release, and dropped subscriptions with enough identity to reject obsolete connection events.
  • Recreate disconnected connections empty. Do not automatically restore their subscriptions; ChainSync should retain or evict local mirrors according to remaining coverage.
  • Keep delayed gRPC duplication in the gRPC layer, not in a WebSocket promotion queue or separate candidate channel.
  • Make capacity exhaustion and transport failures observable. Do not silently drop account updates.

Activity

  1. self-assigned this
    on Sep 19, 2026
  2. added theissue type on Sep 19, 2026
  3. MayurK-cmd commented on Sep 22, 2026

    @MayurK-cmd

    Hey there would love to work on this

  4. bmuddha commented on Sep 22, 2026

    @bmuddha
    CollaboratorAuthor

    @MayurK-cmd thanks, but that's an internal epic, which is handled by the core team

  5. MayurK-cmd commented on Sep 22, 2026

    @MayurK-cmd

    Ahh no worries can you point to any issues or repos of magic blocks for which i can contribute to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions