Subscribe to a stream of tagged slot lifecycle updates emitted by the validator.
Source
This subscription is unstable. The format may change in the future and may not always be supported.
{"jsonrpc": "2.0","id": 1,"method": "slotsUpdatesSubscribe"}
params
Noneresult
Response
{"jsonrpc": "2.0","result": 0,"id": 1}
integer
Subscription id. Pass this to slotsUpdatesUnsubscribe.
Notification format
Notifications are delivered as slotsUpdatesNotification. The payload is the
tagged slot-update object serialized as JSON with a type field.
type value | Fields present |
|---|---|
firstShredReceived | slot, timestamp |
completed | slot, timestamp |
createdBank | slot, parent, timestamp |
frozen | slot, timestamp, stats |
dead | slot, timestamp, err |
optimisticConfirmation | slot, timestamp |
root | slot, timestamp |
timestamp is emitted as a Unix timestamp in milliseconds.
The example below shows a frozen notification captured from a local validator.
Other variants use the field matrix above.
{"jsonrpc": "2.0","method": "slotsUpdatesNotification","params": {"result": {"type": "frozen","slot": 356,"timestamp": 1774643712834,"stats": {"numTransactionEntries": 1,"numSuccessfulTransactions": 1,"numFailedTransactions": 0,"maxTransactionsPerEntry": 1}},"subscription": 4}}
jsonrpc
string
Always "2.0".
method
string
Always "slotsUpdatesNotification".
params
object
Notification wrapper with the serialized slot-update payload and the subscription id.
Is this page helpful?