Digital AssetPassports
One physical unit. One verifiable identity.
A Digital Asset Passport is the public disclosure profile of an approved registry unit: its identity, its governed statuses, its approved evidence and its complete version history. Passports never display fictional data — every field reflects only what has been supplied, reviewed and approved.

- Unique Identity
- Live Statuses
- Immutable History
- QR Verification
- Machine-Readable
What a Passport Contains
Unique Identity
Every approved lot, batch, container or coil receives a unique public passport ID tied to its physical identity.
Live Statuses
Verification, custody, reserve, tokenization and redemption statuses are shown exactly as approved — defaults remain Pending.
Governed Evidence
Laboratory reports, certificates and inspection records are linked only after review and approval.
Immutable History
Every change is versioned in an append-only history that cannot be edited or removed.
QR Verification
Each passport carries a QR code so a physical unit can be checked against its public record.
Machine-Readable
A public JSON profile allows systems and auditors to consume passport data programmatically.
From Draft Record to Public Passport
- 1
Record Creation
A registry record is created as a draft with its passport ID reserved.
- 2
Review
Documentation and statuses pass through a documented review workflow.
- 3
Approval
Maker-checker approval is required before any publication.
- 4
Publication
Only published records appear publicly — drafts remain invisible.
- 5
Public Passport
The passport page and JSON profile go live with QR verification.
- 6
Open Updates
Every subsequent change appends a new version to the public history.
Physical-to-Digital Check
Each passport carries a QR code linking the physical unit to its public record.
- Scan the unit's QR label
- Compare identifiers and seals
- Review approved statuses and history
Machine-Readable Profile
Every published passport exposes a public JSON profile for programmatic verification.
- Stable public schema
- Statuses and version history
- Suitable for auditors and integrators
Integrity by Design
Passport data is protected by the same controls as the registry itself.
- Append-only, hash-chained audit trail
- Maker-checker publication workflow
- Draft records are never publicly visible
No passport displays fictional quantities, valuations, custodians or verification claims.
Empty fields stay unpublished until a value is supplied and approved.
See the Passport Architecture in Action.
Browse the registry for published records, or open the product passport to see identity, statuses and version history of a purchased unit.