What ships
How it works
- 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.
- 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.
- List and sell. Chunks roll up into datasets the owner lists. Buyers verify the machine’s signatures and chunk hashes before paying.
- 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.
Sell across chains
Buyers pay on the chain a listing quotes in — the transfer rail covers peaq, Base, and , and the rail covers signed pay-per-request authorizations — while the sale record and the machine’s identity stay canonical on peaq. Broader omnichain settlement is still rolling out — 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.Distribution & P2P delivery
Purchases, payment rails, and delivery — buyer access over S3, or encrypted chunks streamed machine-to-machine over P2P.
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.

