Cirpass 2 Reference Architecture Json-Ld DPP

CIRPASS-2, the EU-funded project piloting Digital Product Passports across textiles, electronics, tyres, and construction, published its updated reference architecture on 10 June 2026 recommending JSON-LD as the default exchange format — which is what a W3C Verifiable Credential already is.

Why AuthiChain

• A Verifiable Credential is JSON-LD by construction: the @context field the recommendation asks for is already required in every record protocol/SPEC.md §3 defines
• Modular, extensible passport templates across product groups match how credentialSubject already varies by category without changing the record’s outer structure or its signature mechanics
• CIRPASS-2 is a pilot project’s technical recommendation, not a binding standard — the legal requirement stays whatever a category’s ESPR delegated act specifies once adopted

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

Is the CIRPASS-2 reference architecture legally binding?

No — it is a recommendation from an EU-funded pilot running through April 2027, intended to inform the Commission’s eventual technical implementing acts. Binding requirements are set separately by each category’s delegated act.

Does the JSON-LD recommendation mean our records need reformatting?

Not if they are already W3C Verifiable Credentials — JSON-LD is the format VC Data Model 2.0 uses. The recommendation aligns with that base format rather than replacing it.