RPC: ListTransfers

Reads the transfer log: what this peer received, from whom, under which claimed scope, and what became of each blob.

8 October 2026

ContentPeople2CommentsCitationsAttributes0

Fetching schema…

Part of Stem. This page defines the ListTransfers method of the sync RPC specification. It is the inbound half of privacy bookkeeping.

The formal schema is attached as the schemaDefinition of this page: a struct {key, input, output} with key pinned to ListTransfers.

Reads the transfer log: what this peer received, from whom, under which claimed scope, and what became of it.

Input

field	type	required	meaning
`scope`	data/scope	no	Only transfers claiming this scope.
`peer`	data/peer-id	no	Only transfers from this peer.
`page`	rpc/type/page	no	Pagination.

Output

field	type	required	meaning
`transfers`	list of data/transfer	yes	Matching transfers, newest first.
`nextPageToken`	string or null	yes	Token for the next page, or null.

Rules

Filters combine with AND. Results are newest first with page pagination.

The log is local-only state; it is never synced or served.

Per-blob verdicts are kept alongside each transfer and reachable through the database; this method returns the counts.

Today (HM24)

No equivalent. HM24 has per-site write throughput counters in its debug pages but no record of who sent what.

Example

{"key": "ListTransfers", "input": {"peer": "12D3KooWAb…", "page": {"pageSize": 10}}}

{"transfers": [
  {"id": "tx-7f3a", "peer": "12D3KooWAb…", "account": {"/": {"bytes": "7QEC44…"}}, "scope": {"space": {"/": {"bytes": "7QEA…"}}, "node": "bafyrein6a6wfhym6l3vfz5zfkkibj5j6wjibagi3mnbqnspuq2idw52ijb", "depth": "subtree"}, "ts": 1759910470000, "received": 3, "indexed": 2, "stashed": 1, "rejected": 0}
], "nextPageToken": null}

Input

Output

Rules

Today (HM24)

Example

See also