Part of Stem. This page defines the rpc/type/sync-status message type used by the sync RPC specification. Sync and SyncStatus return it.
The formal schema is attached as the schemaDefinition of this page.
Progress and outcome of syncing one scope.
Fields
field | type | required | meaning |
|---|---|---|---|
| yes | The scope. | |
| one of | yes | State of the latest run. |
| data/version or null | yes | The version of the scope's node this peer holds, or null. |
| timestamp or null | yes | When the last run finished. |
| yes | Peers contacted in the last run. | |
| yes | Peers that answered. | |
| yes | Blobs the run learned it lacked. | |
| yes | Blobs received so far. | |
| string or null | yes | Last error, or null. |
Rules
version is the version of the scope's node as held locally, whatever the run's state.
Counts are for the latest run only.
error is a human-readable string for display and is not part of the protocol's error enum.
Today (HM24)
HM24's DiscoverEntityResponse carries state, version, timing and a progress struct with peers found, synced and failed and blobs discovered, downloaded and failed. The fields are renamed and typed.
Example
{"scope": {"space": {"/": {"bytes": "7QEA…"}}, "node": "bafyrein6a6wfhym6l3vfz5zfkkibj5j6wjibagi3mnbqnspuq2idw52ijb", "depth": "subtree"}, "state": "done", "version": "bafy…13", "lastRun": 1759910470000, "peersAsked": 2, "peersOk": 2, "blobsWanted": 2, "blobsReceived": 2, "error": null}See also
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime