Digital Product Passport Access Rights

ESPR splits Digital Product Passport access into tiers — public, professional/economic-operator, and authority — and the registry rule this protocol already implements, a permanent URL with no authentication, is exactly what the public tier requires.

Why AuthiChain

• Annex XIII and the Article 77(9) implementing act govern which fields each tier sees; the split is defined per product-group delegated act, not by this protocol
• SPEC.md §6 requires records to resolve from a permanent URL without authentication — verification that requires an account is not public verification, and that is the public tier by definition
• Field-level restriction for confidential technical data is not in spec v0.1.0 — every field in a record issued today is visible to anyone who resolves its URL, which is the public-tier behavior and not yet the professional or authority tiers

How it works

Issue a unique identifier per unit, anchor its record on-chain for tamper-evidence, and let anyone verify it with a single scan. Plans start at $49/mo.

FAQ

Does this protocol already support ESPR-style tiered access?

Not yet — v0.1.0 issues one record with one visibility level. Tiering confidential fields for repairers, recyclers, or authorities is a real requirement the delegated acts will define, and it is not built here.

Is a single public record still useful before tiering exists?

Yes, for the tier ESPR requires to be free and unauthenticated — which is how every record resolves today.