Industry of Things Performance
How do you know a machine economy is working?
The Northstar
Value per verified event, trending up as hardware cost trends down.
A verified event is a signed reading from an attested device, anchored on-chain. The economic test: is anyone willing to pay more than the marginal cost of producing one? If yes, the network compounds. If no, token emissions are subsidising noise.
| Dimension | Question | Good Signal |
|---|---|---|
| Price per event | Is the market paying for signed data? | Bid price > emission subsidy |
| Cost per event | Is hardware dropping faster than payments? | Margin expands without raising fees |
| Coverage | Are events where demand is? | Events cluster in high-JTBD zones |
| Attestation integrity | Can events be faked cheaply? | Fraud rate < insurance threshold |
| Operator retention | Do honest operators stay? | Churn drops as network matures |
Tightness Score: 2/5
No agreed northstar exists across the industry. Some networks count device installs, some count scans, some count total value locked. The fragmentation mirrors the tribal split — Explorers measure novelty, Automators measure uptime, Validators measure fraud. Until the three agree on one number, the market sees noise.
Leading Indicators
Signals that arrive before the lagging numbers confirm the story.
| Indicator | What It Predicts | Off-Track Means |
|---|---|---|
| New operator onboarding rate | Hardware cost crossing a threshold | Subsidy addiction, not product pull |
| Price paid per event by non-holders | Real demand outside the token circle | Network is a closed loop, not a market |
| Firmware attestation rate | Integrity of the data at the edge | Reader tampering goes unchecked |
| Dispute rate on events | Trust in the oracle layer | Bad data reaching settlement |
| Cross-network interop calls | The industry is converging on standards | Walled gardens are winning |
Remedial Actions
What to do when indicators go red.
| Red Indicator | Remedial Action |
|---|---|
| Non-holder price flat | Partner with one enterprise buyer, prove the JTBD |
| Operator churn rising | Raise attestation rewards, slash free riders |
| Firmware attestation weak | Ship signed firmware update, rotate compromised keys |
| Dispute rate rising | Introduce second-source cross-check, raise stake requirements |
| Interop calls stalled | Publish schema, subsidise the first three integrators |
Acceleration Signals
When to push harder instead of pulling back.
| Green Signal | What to Accelerate |
|---|---|
| Enterprise buyer repeats orders | Open a direct sales channel for verified events |
| Insurance underwrites on your data | Package as an oracle product, charge a premium |
| Hardware cost drops 30% | Subsidise operator onboarding while window open |
| Regulator references the chain | Propose the schema as the reporting standard |
| Rival network asks to interop | Lead the standard instead of following it |
Context
- Principles — Why nomenclature precedes measurement
- Data Footprint — The commissioning instrument
- Reality Metrics — How to build a northstar from verified events
- Economy of Things — Protocol layer that makes events verifiable
Questions
If the northstar is value per verified event, which network is closest to proving it — and which one is furthest?
- When does subsidy stop being bootstrap and start being addiction?
- What's the fastest way to find a non-holder buyer for signed events?