Use case
Digital product passport
A structured history of a product for a buyer or a regulator. It is a data model and an issuer problem before it is a chain problem.
A manufacturer must publish defined facts about a product — materials, repair, end of life — to parties who were not in the factory.
When shared machinery earns a place
When many issuers must append to a history and a silent deletion must be detectable.
When it does not
A single brand publishing a page about its own product.
Conventional-first
Product database, public or permissioned API, signed export.
Readers trust you to keep old versions.
Hybrid
Credential per event, status, hash of the passport version.
Identity of later issuers is the real work.
On-chain-native
Usually unnecessary. A token of a serial number still needs the off-chain facts.
Public serial data can be a privacy problem for owners.
Patterns
Components
- Spruce SSIGreen — compatible use if you keep the notices
- walt.id IdentityGreen — compatible use if you keep the notices
- PonderGreen — compatible use if you keep the notices
Questions a person still has to answer
- Which fields are mandatory, and who defined them?
- Can an owner be identified from the passport?