Use case
Connected-asset provenance
A history of a physical thing, signed by devices or by custodians. A reward token for a sensor is a different product, and not this one.
A buyer, insurer, or recycler needs to know where an asset was and who attested to its condition.
When shared machinery earns a place
Multiple custodians who do not share a database, and a need to detect a rewritten history, can justify signed events and an anchor.
When it does not
The manufacturer already trusts its own database. Writing every telemetry point to a public chain is usually waste.
Conventional-first
Device identity in your IAM, time-series store, exportable signed report.
Counterparties trust your export.
Hybrid
Device credential, signed events, batch register, optional anchor of the batch hash. Evidence files stay off chain.
Revoking a compromised device is the hard part.
On-chain-native
Rejected as a default. Cost, privacy, and useless precision.
Do not generate this stack unless a written reason survives review.
Patterns
Components
- Spruce SSIGreen — compatible use if you keep the notices
- go-libp2pGreen — compatible use if you keep the notices
- Kubo (IPFS)Amber — conditions, and a legal review before you copy it in
- PonderGreen — compatible use if you keep the notices
Read before you build
Questions a person still has to answer
- Who attests, the device or the operator?
- What is the retention of location data?
- Can a buyer verify without receiving the whole history?