slotsUpdatesUnsubscribe

slotsUpdatesUnsubscribe shuts down a slot-lifecycle stream opened with slotsUpdatesSubscribe on the same WebSocket connection. Pass the integer subscription id from the subscribe ack; the server answers result: true and stops emitting slotsUpdatesNotification frames for that id. Other subscriptions sharing the connection are not affected.

Because the updates stream fires for every stage of every slot — routinely ten or more frames per second, around a million a day — it is the kind of subscription you should treat as a scoped measurement instrument, not ambient background noise. Turn it on for the duration of a task and turn it off when the task ends: a propagation-latency benchmark that has collected its sample window, a leader-skip monitor that only runs during your validator's assigned slots, an incident investigation that was watching for dead slots while a cluster event unfolded, or a trading system that only consumes optimisticConfirmation timing during active sessions. Leaving the firehose attached to a connection that also carries application subscriptions inflates parse latency for everything else on the socket, so releasing it promptly is a performance measure as much as a hygiene one.

Lifecycle semantics follow the common Pub/Sub contract. The id exists only within the current WebSocket session; after a reconnect the server has already discarded the subscription, and replaying the old id yields -32602 (invalid subscription id) — the same error a duplicate unsubscribe produces. Given the stream's rate, expect a burst of already-buffered notifications to arrive after your unsubscribe frame and before (or even just after) the ack; route by known subscription ids and silently drop the rest. There is no replay on resubscribe — the events that occurred while you were detached are gone, which is fine for an instrumentation stream. Closing the socket releases this and all other subscriptions in one step.

Positional params array: [subscriptionId].

Response fields

• Scoped instrument: subscribe for the measurement window, unsubscribe when it closes — don't leave the firehose running.
• Post-unsubscribe burst: buffered frames will trail the request; filter by ids you still track.
• No replay: detached time is lost; that is expected for this stream.
• Related methods: slotsUpdatesSubscribe.