Skip to main content
Stream is the data side of the machine economy. A machine signs the data it generates, encrypts whatever is sensitive, and sells access to it, so robots and devices earn from the one thing they produce constantly: machine data. Where Scale lets a machine buy services and Monetize lets it sell services, Stream lets it sell data. It builds on the identity a machine receives at Activate — , , and a cross-chain — and uses that identity to prove which machine produced a given .

​
What ships

ComponentDescription
peaqOS Edge AgentA persistent on-machine process, installed as a ROS 2 node, that signs, encrypts, and ships the data the machine generates. It provisions identity from Activate and runs the signing pipeline automatically once configured.
Data Event MapThe policy file that controls what streams out: topic subscriptions, per-field rules (include, exclude, encrypt, anonymize), signing policy, and output destinations.
Signed data packagesEvery package carries the machine’s peaqID, a timestamp, a schema version, and a sequence number, signed with the machine’s key. Anyone verifies it with the public key derived from the DID. Field rules run before signing, so protected fields never leave in the clear while the package stays verifiable.
Chunking + encryptionData is grouped into bounded , each encrypted under its own key and linked into a tamper-evident . Chunks roll up into with a .
Data marketplaceOwners list datasets; buyers verify signatures and hashes, pay, and receive an — the purchased chunk keys re-wrapped to their public key. The backend stores manifests and grants, never plaintext.
DistributionSigned, encrypted chunks leave over the owner’s chosen vector: a P2P feed keyed by Machine , cloud storage, , or a direct API.

​
How it works

  1. Install and configure. The Machine Owner installs the as a ROS 2 package and writes a : which topics to read, which fields to keep, drop, or encrypt, and where signed data goes.
  2. Sign and encrypt. As data is captured, field rules run first, then the package is signed with the machine’s key and grouped into encrypted chunks.
  3. List and sell. Chunks roll up into datasets the owner lists. Buyers verify the machine’s signatures and chunk hashes before paying.
  4. Grant and deliver. After payment, an access grant re-wraps the purchased chunk keys to the buyer’s key. The buyer decrypts only what they bought.
See Data streams for the full trust model.

​
Sell across chains

Buyers pay on the chain a listing quotes in, and the sale record and the machine’s identity stay canonical on peaq. Cross-chain settlement across and is part of the omnichain rollout — see the roadmap.

​
Build with Stream

Data streams (concept)

The trust model: signing, chunk chains, encryption, datasets, and buyer access grants.

Stream SDK reference

The stream module for JavaScript and Python.

Stream Edge Agent (ROS 2)

Run the on-machine node that signs, encrypts, chunks, and streams your data.

peaqOS CLI: stream

Publish signed, encrypted chunks and grant buyer access from the terminal.

Buy data (marketplace API)

The buyer side: discover listings, order, pay, and download as a Context Provider.

Roadmap

Where Stream sits and what ships next.