Skip to content
← Back to Blog
Who Issued This Digital Product Passport? What Timestamps, Ledgers and the vLEI Prove
eu-regulations

Who Issued This Digital Product Passport? What Timestamps, Ledgers and the vLEI Prove

A digital product passport has to answer three questions: when the data was written, whether it has changed, and who issued it. A qualified eIDAS timestamp and a blockchain anchor answer the first two. The third needs a qualified electronic seal or a verifiable LEI, and the EU texts show why.

Anyone who scans a digital product passport sees data about a product: materials, carbon footprint, a battery's capacity. Before trusting it, a buyer, a recycler or a market surveillance authority has three questions:

  1. When was this data written?
  2. Has it changed since?
  3. Who issued it?

The first two have clear answers in EU law and in standard cryptography. The third is where most passports are weaker than they look. This article explains what each tool proves, what the EU texts ask for, and what a small manufacturer should do before the battery passport becomes mandatory on 18 February 2027.

What the EU asks a passport to prove

The Ecodesign Regulation (ESPR) asks that the digital product passport be designed and operated to ensure data authentication, reliability and integrity and a high level of security and privacy (Regulation (EU) 2024/1781, Article 11). It does not name a technology. Neither the ESPR nor the Battery Regulation mentions blockchain or distributed ledgers: we searched both texts on EUR-Lex.

So the job is defined by its result. A passport is trustworthy when someone outside your company can check when the data was fixed, that it is unchanged, and that it really comes from you.

When was the data written? The qualified eIDAS timestamp

eIDAS defines an electronic time stamp as data that binds other data to a particular time, establishing evidence that the data existed at that time (Article 3, point 33). A qualified electronic time stamp goes further: it enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data it is bound to (Article 41(2)).

To be qualified, the timestamp must bind date and time to the data so that any change is detectable, use an accurate time source linked to UTC, and be signed or sealed by a qualified trust service provider (Article 42(1)). Every Member State publishes a trusted list of these providers, which you can search in the Commission's eIDAS Dashboard. Our page on qualified eIDAS timestamps for product passports covers the details.

Has it changed? Fingerprints and a public ledger

A SHA-256 fingerprint (hash) of the passport changes completely if a single character of the data changes. Only the fingerprint needs to leave your systems, never the data.

Anchoring that fingerprint on a public blockchain lets anyone check it later without asking you or your software provider. In legal terms, eIDAS 2.0 calls this an electronic ledger: records whose integrity and chronological order are ensured (Article 3, point 52). A qualified electronic ledger, which gets a presumption of integrity and of correct chronological order, must be run by qualified trust service providers (Articles 45k and 45l). A public blockchain run by anyone is therefore an ordinary electronic ledger. It is still admissible as evidence (Article 45k(1)), and its value is independent verification, not a legal presumption.

Who issued a digital product passport? The weak spot

Here the EU texts say less.

The ESPR lists among the passport's possible content information related to the manufacturer, such as its unique operator identifier (Annex III, point (g)). It defines that identifier as "a unique string of characters for the identification of an actor involved in a product's value chain" (Article 2, point 31), and requires it to follow recognised standards (Article 12). In the battery passport, data point 3 of the Commission's guidance (version 3.2, 19 October 2026) is the manufacturer's name, registered trade name or registered trademark.

Both are useful: they tell you who the passport claims to come from. Neither proves it. An identifier or a name is text inside the data, and anyone can type text. A timestamp and an anchor prove that the text existed at a time and has not changed. They do not prove that the company named in it wrote it.

What actually proves the issuer

A qualified electronic seal. eIDAS defines an electronic seal as data attached to other data to ensure its origin and integrity (Article 3, point 25). A qualified seal enjoys the presumption of the integrity of the data and of the correctness of the origin of the data to which it is linked (Article 35(2)). It is the company equivalent of a qualified signature, and the qualified certificate behind it is issued only after a qualified trust service provider has verified the identity of the company (eIDAS Article 24(1)).

The EU already uses it for exactly this purpose. Under Implementing Regulation (EU) 2026/1778 on the DPP Registry, an economic operator must be verified before registering passports, and companies are verified with a qualified electronic seal (Articles 4 and 5). The Registry's own proof of registration is sealed the same way (Article 9).

The verifiable LEI (vLEI). The Legal Entity Identifier is the global company identifier already used in finance. GLEIF describes the vLEI as a decentralised digital identity that lets counterparties verify by software the identity of a legal entity and the authority and role of the people acting for it. vLEIs are issued by Qualified vLEI Issuers and the identifier is standardised in ISO 17442-3 (2024). On 18 November 2026 a first proof of concept linking vLEI credentials to digital product passports was announced, with pilots with manufacturers planned next. It is still an early test.

Digital product passport with eIDAS timestamp and blockchain: what each layer proves

LayerAnswersLegal effect in the EUWho can check it
Qualified eIDAS timestampWhen the data existedPresumption of accurate date, time and integrity (eIDAS Art. 41(2))Anyone, with the token and the provider's certificate
Hash anchored on a public blockchainThat the data is unchangedAdmissible as evidence, no presumption (eIDAS Art. 45k(1))Anyone, with a block explorer
Unique operator identifier or manufacturer nameWho the passport claims to come fromNone on its own: it is dataAnyone can read it, nobody can verify it from the passport alone
Qualified electronic sealWho issued the dataPresumption of integrity and correct origin (eIDAS Art. 35(2))Anyone, against the EU trusted lists
vLEI credentialWhich legal entity, and who acts for itOutside eIDAS: GLEIF's vLEI trust frameworkAnyone with vLEI verification software

At Hoken Pass we cover the first two today. Every published version of a passport gets a qualified timestamp, paid plans add an anchor on the EOS blockchain, and anyone can recheck both from the public file on the passport's verify page. The company name on a passport is the one the company entered in its settings. For origin, the Registry's seal check is the real gate today, which is why our digital product passport software for SMEs leaves registration in the Registry to the company, with its own EU Login and seal.

What a small manufacturer should do now

  1. Check your timestamps. Ask your provider which qualified trust service provider issues them, then find that provider on the trusted list yourself. If it is not listed with a qualified time stamp service, the timestamp is not qualified.
  2. Choose your operator identifier. Decide which identifier goes in your passports for your company (for example an LEI, an EORI or a GS1 GLN) and keep it identical everywhere. Check whether your company already holds an LEI.
  3. Plan your seal. To register passports in the EU DPP Registry, your company will need to be verified with a qualified electronic seal. Plan it well before February 2027.
  4. Watch the vLEI. If your customers or your sector start asking for it, you will need an LEI first, then a vLEI from a Qualified vLEI Issuer.

For the full picture on timestamps and ledgers, see our guide on what a digital product passport with eIDAS timestamp and blockchain really needs, and for batteries our battery passport page.

Frequently asked questions

Does a unique operator identifier prove who issued a digital product passport?

No. The ESPR defines it as a unique string of characters that identifies an actor in the value chain (Article 2, point 31). It says who the passport claims to come from. Proof of origin needs something cryptographic tied to a verified identity, such as a qualified electronic seal.

Is blockchain required for a digital product passport?

No. Neither the ESPR nor the Battery Regulation mentions blockchain. The ESPR asks for data authentication, reliability and integrity (Article 11). A blockchain anchor is one way to let anyone verify integrity independently.

What is the difference between a qualified timestamp and a qualified electronic seal?

A qualified timestamp proves when data existed and that it is unchanged (eIDAS Article 41(2)). A qualified electronic seal proves which legal person the data comes from and that it is unchanged (Article 35(2)). A passport can carry both.

What is a vLEI?

The verifiable version of the Legal Entity Identifier, described by GLEIF as a decentralised digital identity for organisations. It lets software verify a company's identity and the role of the person acting for it. It is issued by Qualified vLEI Issuers.

When does the battery passport become mandatory?

From 18 February 2027 for EV batteries, LMT batteries and industrial batteries above 2 kWh, under Article 77 of Regulation (EU) 2023/1542.

Sources

Start free: https://www.hokenpass.com