DSR Protocol · Disruption brief
Resolver-first vs legacy
One physical code. One resolver. Promotion, authentication & the Digital Product Passport from the same tap.Prepared for premium & luxury brands
The choice is architectural. A resolver-first platform puts a single GS1 Digital Link on the piece and serves promotion, authentication and the DPP from the same tap — with verification and telemetry running inside your own resolver (zero-egress). A legacy or centralised platform routes each tap through a vendor cloud and, increasingly, a blockchain layer the DPP regulation does not require.
Enterprise depth with the simplicity of one web-standard link — your domain on the tag, your keys, your data. No blockchain, no per-scan tax, no lock-in.
Head-to-head
| Dimension | DSR Protocol (resolver-first) | Legacy / centralised platform |
|---|---|---|
| Core architecture | Resolver-first — a deterministic, tenant-isolated decision graph you own | Vendor cloud, increasingly wrapped around a distributed ledger |
| One code, many jobs | A single GS1 Digital Link serves promotion, authentication & the DPP from the same tap, audience-aware | Separate systems / codes; each capability is another integration and another hop |
| Where a tap is verified | In your own resolver (standard AES-CMAC) — one round-trip, no external call | In the vendor cloud — commonly a second hop, often metered per scan |
| Data posture | Zero-egress — verification & scan telemetry stay inside your platform | Scan data lands in the vendor’s platform, on the vendor’s terms |
| Blockchain | None — not required by the EU DPP direction (ESPR / EN 18222) | A ledger layer that is carbon-intensive, infrastructure-heavy and adds cost without a DPP benefit |
| Carbon & infrastructure | Right-sized resolver — a low, predictable footprint | Ledger nodes / consensus add continuous energy and operational overhead |
| NFC hardware | Right-sized: NTAG 424 DNA where value is high, NTAG 213/215 at entry-tier volume | One-size tag tied to the vendor’s ecosystem |
| Standards & portability | GS1 Digital Link + JSON-LD — portable; your domain on the tag | Platform / ledger lock-in; leaving usually means export and re-encoding |
| Per-scan economics | No per-scan verification fee — standard AES in your resolver | Verification commonly metered per scan or tiered |
Why blockchain is the wrong tool for a Digital Product Passport
- The EU DPP direction (ESPR / EN 18222) is built on GS1 Digital Link + W3C Verifiable Credentials + a resolver — a ledger is explicitly not required.
- A distributed ledger is carbon-intensive and infrastructure-heavy, adding continuous energy and operational cost for no passport benefit.
- Ledger transparency can conflict with trade-secret obligations (ESPR Art. 10/11); routine acts — correction, revocation, audience-aware redaction — are awkward on an append-only chain.
What changes for the maison
One physical codeAdd a promotion or a customs dossier without reprinting or re-tagging.
Your domain on the tagGS1 Digital Link on your own domain — not the vendor’s.
Right-sized trust424 DNA on fine pieces; 213/215 at affordable, entry-tier volume.
Your data stays yoursZero-egress telemetry; grey-market signals surface in-house.
Live demonstration:
dsrprotocol.com · 26 September 2026
/resolver-demo · Architecture: /supply-chain-sketchdsrprotocol.com · 26 September 2026
Scan to view live