Anchoring doesn’t make data true. It makes it un-rewritable. That distinction — between a product record and product evidence — is the most mis-sold idea in the Digital Product Passport market. This page explains, from the EU texts, what anchoring proves, what it can never prove, and how to test any vendor who uses “blockchain” as a synonym for trust.

The problem: data that can be quietly rewritten

A passport is only useful if its past can be trusted. Product data lives for years — through repairs, resales and recycling — and passes through many hands. In an ordinary database, every record can be edited after the fact, leaving no trace: a recycled-content figure raised, a date moved, a test result replaced. For a document that authorities, customs and buyers will rely on, silent editability is the flaw.

How anchoring works

Anchoring has three steps. First, the record is reduced to a hash: a fingerprint of its exact content, which changes completely if even one character changes. Second, that fingerprint is written, with its time, into an append-only ledger: entries are added in sequence and cannot be altered or deleted without breaking the chain of proofs that follows them. Third, anyone authorised can recompute the fingerprint and compare it with the anchored one. Match: the record is exactly the record that was anchored. Mismatch: something changed, visibly.

What anchoring proves

Anchoring — the four proofs

  • Existence at a time: this exact record existed no later than its anchoring moment;
  • Integrity since then: the record has not been altered after anchoring;
  • Order: records sit in a unique sequential chronological order, so versions cannot be re-sequenced or backdated;
  • Origin, when records are authenticated: a signed or sealed record ties its fingerprint to the actor who submitted it.

What anchoring does not prove

Here is the part the marketing leaves out. Anchoring says nothing about whether the data was true when it was entered: a false recycled-content figure, hashed and anchored, is a false figure with an excellent proof of integrity. It also does not prove that a record describes the physical product in front of you — that link is made by the unique identifier and the data carrier — and it does not prove completeness: what was never recorded was never anchored. EU law puts those duties where they belong: under Article 77(4) of the Batteries Regulation, the operator placing the battery on the market is responsible for the passport information being accurate, complete and up to date, and under the ESPR the same responsibility sits with the operator placing the product on the market. Technology protects the record; the operator answers for the truth.

What EU law already says

The ESPR does not mandate blockchain — it is technology-neutral — but it mandates the properties anchoring delivers: under Article 11(g) of Regulation (EU) 2024/1781, “data authentication, reliability and integrity shall be ensured”, and under Article 11(h) passports must be designed so that “a high level of security and privacy is ensured and fraud is avoided”. Regulation (EU) No 910/2014 (eIDAS), as amended by Regulation (EU) 2024/1183, then gives ledgers a legal home: it defines an electronic ledger as a tamper-proof electronic record providing authenticity and integrity of its data, accuracy of their date and time, and their chronological ordering. Article 45k adds the legal effects: an electronic ledger cannot be denied legal effect or admissibility merely because it is electronic, and records in a qualified electronic ledger enjoy the presumption of their unique and accurate sequential chronological ordering and of their integrity. Article 45l sets the bar for “qualified”: created and managed by qualified trust service providers, establishing the origin of its records, ensuring that ordering, and recording data so that any subsequent change is immediately detectable. Qualified time stamps (Article 41(2)) and qualified archiving (Article 45i) carry matching presumptions of integrity — and of origin, for archiving. The limit matters: the strongest presumption attaches to qualified ledgers run by qualified trust service providers, a status no vendor should claim loosely.

Governed, not public

None of this requires a public crypto network. A governed, permissioned ledger — known participants, rules on who may write and read, predictable costs — delivers the same tamper-evident properties without tokens or crypto exposure, and with personal data handled under the GDPR: the passport data stays in controlled systems; what is anchored is its fingerprint. For regulated product data, governance is not a compromise. It is the requirement.

Five checks when a vendor says “blockchain”

  • Show me the verification: can you recompute a fingerprint and check it against the anchor, independently, today?
  • What exactly is anchored: the full record, its fingerprint, or a marketing claim?
  • Who can write, and who governs: named participants and rules — or an anonymous public chain?
  • What happens on exit: do the anchors and the means to verify them survive a change of provider?
  • Where is the honesty line: does the vendor state in writing that anchoring proves integrity and not the truth of your source data?

How Ledger Consortium helps

Ledger Consortium aggregates the product data held by you and your suppliers and anchors each passport record on a governed blockchain, so every version is timestamped, ordered and tamper-evident — data turned into evidence that customers, repairers, authorities and customs can check. The boundary, plainly: anchoring proves a record existed and has not been altered; it does not certify that the data a client supplied was true — accuracy remains the operator’s responsibility. Costs are predictable, there is no token and no crypto exposure, and the platform is GDPR- and eIDAS-aligned. In Italy, the Ledger DPP is distributed by Il Sole 24 Ore (Valore24), whose channel onboards dozens of companies per month. Verify a working passport in our live demo, browse News, and read the rules for the providers who host your data in What a DPP Service Provider May — and May Not — Do With Your Data.