Insights on Crypto Payments, Infrastructure, and Operations

Signature Subscription

Pronunciation: SIG-nuh-cher sub-SKRIP-shun

Also known as: Transaction Signature Subscription, Solana signatureSubscribe

Definition

Signature Subscription is a Solana WebSocket RPC subscription that sends status notifications for one specified transaction signature until a terminal confirmation notification is delivered. It monitors transaction status and is unrelated to subscribing for cryptographic signing services or reusable signature authorization. A production implementation should use the correct signature and commitment, handle an optional received notification separately from confirmation, detect disconnects, query transaction status after gaps, and close local resources after termination. The principal risks include treating receipt as confirmation, missed terminal messages after disconnect, wrong commitment assumptions, provider-specific availability, duplicate notifications, and keeping stale subscriptions indefinitely.

Overview

Signature Subscription is a Solana WebSocket RPC subscription that sends status notifications for one specified transaction signature until a terminal confirmation notification is delivered. It monitors transaction status and is unrelated to subscribing for cryptographic signing services or reusable signature authorization.

The principal risks include treating receipt as confirmation, missed terminal messages after disconnect, wrong commitment assumptions, provider-specific availability, duplicate notifications, and keeping stale subscriptions indefinitely. A Signature Subscription handler should acknowledge only after durable receipt when the provider’s retry contract depends on the response.

A production implementation should use the correct signature and commitment, handle an optional received notification separately from confirmation, detect disconnects, query transaction status after gaps, and close local resources after termination. Business actions triggered by Signature Subscription should be idempotent and should verify the current object state before fulfillment or accounting updates.

Useful measures include subscription setup failures, time to received and terminal notification, disconnect rate, fallback query use, duplicate notifications, and unresolved signatures. Signature Subscription is closely connected to RPC Subscription, Transaction Query, and Transaction Submission. Monitoring for Signature Subscription should track delivery age, signature failures, duplicate rate, retry exhaustion, and unresolved business events.

Replay of Signature Subscription should preserve original identifiers and timestamps so historical processing cannot masquerade as a new event. For Signature Subscription, the event identifier, signature result, delivery attempt, and resulting business state should remain connected throughout processing. A receiver should treat transport acknowledgement and successful downstream processing as separate states for Signature Subscription.

The Signature Subscription path should preserve ordering and duplicate evidence so delayed delivery cannot silently overwrite a newer state.

Key Takeaway

Use the correct signature and commitment, handle an optional received notification separately from confirmation, detect disconnects, query transaction status after gaps, and close local resources after termination.

Sources

  1. signatureSubscribe — Solana Foundation (2026-08-03)
  2. Solana RPC WebSocket Methods — Solana Foundation (2026-08-03)
  3. Solana HTTP RPC Methods — Solana Foundation (2026-08-03)