Sui has introduced real-time GraphQL Subscriptions on Mainnet and Testnet, allowing applications to receive blockchain updates without repeatedly polling for new data. Developers can now stream checkpoints, transactions and events through the same GraphQL interface they already use for historical queries, giving wallets, trading applications and monitoring systems a higher-level way to react as new activity reaches the network.
According to Sui’s official announcement, transaction and event subscriptions support filtering aligned with standard GraphQL queries, while most fields available through the Query schema can also be requested in subscriptions. That consistency lets developers define the data they need once and apply similar structures to both historical lookups and live blockchain activity.
GraphQL Can Backfill Before Switching to Live Data
One of the more practical features is the ability to start a subscription from a historical cursor rather than only from the current state. An application can retrieve matching transactions or events from an earlier point, catch up to the chain tip and then continue receiving new records as they arrive. Sui describes this as a “query, catch up, and stay current” workflow that combines historical and real-time data without forcing applications to maintain separate pipelines.
The same mechanism improves recovery after interruptions. If a client disconnects, it can reconnect using the last cursor it processed, backfill the missing activity and then resume live delivery. Sui says the service also handles gaps in its own upstream checkpoint connection. The result is an ordered, contiguous feed designed to reduce the risk that applications miss transactions or events during temporary connection failures.
GraphQL Subscriptions can therefore support use cases ranging from wallets displaying incoming payments to trading interfaces updating positions and monitoring systems reacting to selected smart-contract events. Targeted filtering lets an application consume only the transactions or events relevant to its own packages, addresses or workflows instead of continuously retrieving broader network data. That can also support lighter custom indexing, with developers writing selected subscription results into their own databases.
GraphQL and gRPC Target Different Workloads
The new interface does not replace Sui’s existing gRPC streaming infrastructure. Sui describes gRPC as its lower-level, strongly typed option for high-performance backends, exchanges, infrastructure providers and large indexing systems. GraphQL adds flexibility on top of that data stack by allowing developers to select fields and related information using the same schema and filters already familiar from GraphQL queries.
Architecturally, the two are closely connected. For real-time delivery, GraphQL consumes Sui’s gRPC checkpoint stream, while historical catch-up and data resolution use the gRPC Ledger Service and archival infrastructure when deeper history is required. GraphQL Subscriptions are therefore a higher-level access layer over Sui’s existing data infrastructure rather than an independent real-time system competing with gRPC.
The release also completes a capability that Sui had identified as future work when GraphQL RPC entered public beta in September 2025. GraphQL and the General-purpose Indexer subsequently became generally available for production workloads in March 2026. The next practical milestone will be developer adoption across wallets, analytics tools, trading applications and application-specific indexers, particularly where teams can replace repeated polling with filtered, resumable live streams.