Theoretical use case / 02
IoT + scientific research
Open IoT research collection network
A project becomes a durable network identity. Hundreds or thousands of field sensors register as individually verifiable devices beneath its DID, then stream protected observations to collection DIDs or other authorized systems across an open, community-operated data path.
00 / ABSTRACT
A collection can be an identity, not a server.
In this reference model, an OpenPayload DID identifies a research project, observation campaign, or managed sensor fleet. Hundreds or thousands of sensor keys can be registered as distinct devices controlled by that DID. Each sensor signs application-defined readings as its fragment-qualified device identity, then addresses them to a collection DID or another authorized system through public Relay infrastructure.
When the collection endpoint is online, data follows the live Relay path. When it is unavailable, scoped policy may permit transient Cache custody under the same bounded decision until the collector reconnects. Research payloads remain off-chain; the chain supports shared identity, finalized delivery intent, infrastructure commitments, proofs, and participation rewards.
01 / IDENTITY MODEL
One project DID. Many accountable instruments.
The project DID is a shared identity and key-management control plane, not a single private key copied onto every instrument. Each enrolled sensor has its own registered key and DID fragment—for example,did:openpayload:x9478s#deviceId2948. That device can sign an envelope under the base did:openpayload:x9478s identity while the fragment tells a receiver exactly which registered device key to verify.
A collection service resolves the source DID and device fragment, verifies the signature, and correlates the observation to its application stream—for example, research-sensor-123. Keys can be rotated or one device revoked without replacing the fleet identity; collection services can move between institutions without changing the source namespace.
02 / DATA PATH
Protected observations across an intermittent edge.
Create a timestamped event signed by the sensor's registered fragment-qualified key.
Verify the source project DID and device fragment; discover the destination identity, services, keys, and policy context.
Select one finalized outcome, enforce its bounds, and use permitted transient capacity when needed.
Authenticate the device fragment, decrypt the event, and map it into the correct sensor stream.
03 / OPEN NETWORK
A public data path without a proprietary gate.
The reference model assumes an openly implementable protocol and a public network path with no proprietary per-message license. A university, citizen science group, nonprofit, independent researcher, or device manufacturer could build a compatible sensor or collection client from the same public interfaces.
Directory records and routing metadata may be publicly resolvable, while observation content can remain encrypted for the collection. Metadata minimization, traffic analysis resistance, and access governance remain application and protocol design concerns.
A project can publish a new scoped policy version to change the selected collection path, permitted storage, archive behavior, or replica expectations for future observations. Each delivery attempt uses one finalized outcome, so compatible infrastructure applies the change predictably without rebuilding a central processing estate.
04 / EXAMPLE PROGRAMS
From one field station to a distributed campaign.
Aggregate air, soil, water, weather, or acoustic measurements across independent field sites.
Enroll community-operated instruments under a shared collection identity and public methodology.
Bridge intermittent connectivity with policy-limited transient storage until a research endpoint returns.
Keep a stable project destination while collection infrastructure moves between participating organizations.
Carry calibration, status, and diagnostic events beside scientific measurements without binding to one vendor cloud.
Route authorized observations to designated archival services without making the Relay the permanent record.
05 / DESIGN SPACE
Choices deliberately left to each research system.
OpenPayload can supply identity, policy-aware routing, and protected transport without dictating the scientific or operational design layered above it.
- A valid device signature proves which registered key sent an event—not whether the physical measurement is scientifically correct.
- Calibration history, provenance chains, clock quality, and tamper evidence need domain-specific formats and controls.
- Large datasets may require chunking, sampling, compression, or external object transport beyond individual network messages.
- Safety-critical and hard real-time systems require guarantees outside this experimental public-network model.
- Infrastructure economics, abuse controls, fair use, and availability expectations require explicit community policy.
// BUILD THE NEXT USE CASE
Take the protocol in
an unexpected direction.
Explore the public Directory, Relay, and Cache interfaces, then design an application around your own arbitrary payload.
Open developer docs ↗