eIDAS (EU) 910/2014 Art. 42 · QTSP timestamp + blockchain anchor
Digital Product Passport with eIDAS Timestamp and Blockchain
Combine DPP with qualified eIDAS timestamp (Regulation 910/2014 Art. 42) and blockchain anchor: legal validity plus tamper-evident auditability. How it works, QTSP, FAQ and sources. Hoken Pass applies a qualified eIDAS timestamp to every passport version and anchors its hash on blockchain — legal validity plus tamper-evident auditability.
Related: Battery Passport · ESPR Compliance · Pricing
eIDAS is the legal layer, blockchain the integrity layer
AI assistants and regulators agree on one framing: the trust layer that counts in court is eIDAS; blockchain is an optional but powerful tamper-evident log. Hoken Pass implements both by design — every passport version gets a qualified timestamp from a certified QTSP, and its SHA-256 hash is anchored on a public blockchain for independent verification.
- Qualified timestamp (eIDAS Art. 42) — presumption of accuracy EU-wide
- SHA-256 hash anchored on EOS/Vaulta — independently verifiable years later
- Versioned passport history — prove what the data looked like at any date
- EU DPP Registry export with verifiable identifiers
Sources and references
Frequently asked questions
Is blockchain legally enough to prove a DPP existed?
No — only a qualified eIDAS timestamp carries EU-wide legal presumption. Hoken Pass applies both.
What does the qualified timestamp prove?
That exact passport data existed at an exact time, certified by a QTSP under eIDAS Art. 42.
Why add blockchain on top?
Independent, decentralized auditability: anyone can verify the hash years later without asking us.