Industry of Things Protocols
Standards earn their keep at the seams.
Between a passive tag and a settlement contract sit five stages. Each stage is a decoupling point. Each seam needs a standard, or the chain breaks. This page maps the protocols required and which exist today.
Communication Standards
Zero-confusion intent across the sensor-to-settlement chain. See Economy of Things — Sensor to Settlement for the stage model.
| Stage | Standard Needed | Status | Notes |
|---|---|---|---|
| Sense | Tag + sensor data schemas | Partial | GS1 EPC covers identity, sensing fragmented |
| Interrogate | Reader attestation format | Missing | No cross-vendor attestation standard |
| Attest | Machine DID + signing | Emerging | Peaq DID, W3C DID, competing profiles |
| Anchor | Data availability proof | Emerging | Rollup DA layers, no DePIN-specific profile |
| Settle | Verifiable Intent envelope | Emerging | See Verifiable Intent |
The biggest gap is at Interrogate — there is no cross-vendor standard for "this reader is authentic and its firmware is attested." Every vendor invents its own. A protocol here would unlock the rest.
Best Practices
Patterns that work across networks, even when no formal standard exists.
| Pattern | Why It Works |
|---|---|
| Separate signing from reading | Compromised firmware cannot forge events |
| Anchor first, settle later | Make the ledger immutable before triggering payment |
| Multi-source attestation | Two independent readers must agree for high-value events |
| Rotate keys on a schedule | Limit blast radius of undetected compromise |
| Publish schemas openly | Integrators cannot wire what they cannot read |
| Slash for bad events | Economic gravity keeps operators honest |
Process Improvement Loops
How the protocol layer compounds.
Event captured
↓
Event signed (attest)
↓
Event anchored (immutable)
↓
Event settles (economic outcome)
↓
Outcome feeds back → schema improves → next event is cheaper to verify
Each loop makes the next event cheaper. The compounding is the product.
Tightness Score: 3/5
The protocol layer is mid-maturity. Verifiable Intent and the Intercognitive Standard exist on paper. Peaq provides machine identity. Sui, Base, and Solana provide settlement. The missing piece is the reader attestation profile — a cross-vendor standard for "this interrogator signed this event with an attested key." Until that exists, the chain has a soft middle.
Related Protocols
| Protocol | Layer | Why It Matters Here |
|---|---|---|
| Verifiable Intent | Authorization | Same delegation chain for humans and machines |
| Agent Protocols | Agent coordination | Physical track of the same pattern |
| Intercognitive Protocol | Physical AI coordination | Nine pillars for robots and sensors |
| Smart Contracts | Settlement | Where events become economic outcomes |
| Economy of Things | Machine commerce | The protocol FACT this industry implements |
Context
- Protocols — Three generations of pipe
- Economy of Things — Machine identity and sensor-to-settlement
- Verifiable Intent — Delegation chain
- Trust Architecture — Why benchmarkable standards replace trust-by-assumption
- Standards — What makes a protocol worth following
Questions
Which seam in the sensor-to-settlement chain is the most neglected — and who benefits from leaving it that way?
- What would a reader attestation standard look like if GS1, W3C, and Peaq agreed on it?
- Does the industry need one more protocol, or one fewer?