In supply chain traceability, a blockchain does one specific job: it proves that data recorded on a given date has not been changed since. It does not prove that the data was true when it was entered. Keep those two things apart and the blockchain is a useful, honest tool; mix them up and it becomes a promise it cannot keep.
What actually goes on the blockchain: the fingerprint, not the data
In a well-designed traceability system, supply chain data (batches, processing steps, lab tests, documents) stays in an ordinary database. Only its fingerprint, known as a hash, goes on the blockchain.
A hash is a fixed-length string computed from the data with a cryptographic algorithm. The US standard FIPS 180-4, which defines the SHA family, explains that these fingerprints are used to detect whether a message has been changed after the fingerprint was generated [1]. In practice:
- the same data always produces the same fingerprint;
- change a single comma and the fingerprint changes completely;
- you cannot rebuild the original data from the fingerprint.
Why not put the data itself on the blockchain? Three reasons:
- Confidentiality. A public blockchain can be read by anyone. Recipes, suppliers and prices don’t belong there.
- Cost and size. A short string is cheap to record; a whole document is not.
- Corrections. Wrong data in a database can be corrected; whatever is written on a blockchain stays. With a fingerprint, the correction generates a new fingerprint and the history remains readable.
What a blockchain proves
With the fingerprint on record, you can prove two things.
Integrity. Anyone who has the data can recompute its fingerprint and compare it with the recorded one. If they match, the data is the same as it was then. If they don’t, something has changed.
Date. Every record sits in a block with its own confirmation time. So you can say: “this data has existed in this form since at least this date”.
Italy also has a law on this point. Art. 8-ter of Decree-Law 135/2018 states that storing an electronic document using distributed ledger technologies has the legal effects of the electronic time stamp provided for in Article 41 of the eIDAS Regulation [4]. The same provision, however, tasks the Agency for Digital Italy (AgID) with setting the technical standards these technologies must meet to produce those effects [4]. Before relying on a blockchain record as evidence in a dispute, ask your lawyer how it applies to your case.
What it does not prove
This is the part marketing usually skips.
| A blockchain proves | A blockchain does not prove |
|---|---|
| that the data hasn’t changed since it was recorded | that the data was true when it was entered |
| since when it has existed in that form | who checked it on the ground |
| that anyone can verify this independently | that the physical product matches the data |
If an operator writes “mountain milk” on a batch that isn’t, the blockchain will faithfully preserve that falsehood. Whether the original data is true depends on other things:
- who enters the data and with what permissions;
- supporting documents, such as lab tests, certificates and delivery notes;
- inspections by certification bodies and authorities;
- the change history, which shows who changed what and when.
A blockchain makes it harder to falsify data afterwards. It does not replace the checks beforehand.
Blockchain and GDPR: personal data
The GDPR gives people the right to have their data erased in certain cases (Art. 17), requires that only necessary data be processed (Art. 5) and that systems be designed with data protection in mind from the start (Art. 25) [3]. A public blockchain, where nothing can be deleted, therefore has to be used with care.
On 7 July 2026 the European Data Protection Board (EDPB) adopted version 2.0 of its Guidelines 02/2025 on processing personal data through blockchain technologies [2]. Some useful points:
- when you need to record something relating to personal data, it is better to put only a proof of existence on the chain (a pointer, a cryptographic commitment or a keyed hash) and keep the data needed to verify it off chain [2];
- even the hash of a piece of personal data is still personal data under the GDPR [2];
- a plain hash, without a secret key or “salt”, is generally not enough to protect personal data on a public blockchain [2].
The rule of thumb: don’t put personal data on the chain, not even as a fingerprint, if you can avoid it. Product supply chain data (batches, quantities, dates, company sites) is usually not personal data, but watch out for operator names, signatures and data about individual small producers.
The EU regulation on the digital product passport (ESPR) points the same way: customers’ personal data must not go into the passport without their explicit consent [5].
How to verify on a public explorer
An explorer is a website that shows the blocks and transactions of a blockchain. On a public blockchain anyone can open it, no account needed. Verification works like this:
- From the product passport or the document, take the recorded fingerprint and the transaction reference.
- Open the transaction on the explorer and check that it contains that same fingerprint and the block date.
- If you have access to the original data, recompute the fingerprint with the same algorithm and compare.
The value lies in the fact that you don’t have to trust whoever is showing you the data: you do the comparison yourself, on a ledger that neither party controls alone.
When it makes sense and when it doesn’t
It makes sense if:
- several companies exchange data and none wants to depend on another’s database;
- a certifier, a customer or an authority must be able to verify independently;
- you want to be able to prove, years later, that a record history hasn’t been tampered with.
It is of little use if:
- the data stays inside a single company and no outsider needs to verify it;
- you hope the blockchain will replace inspections, lab tests and certifications;
- you want to put the data on it in plain text.
Frequently asked questions
If data on the blockchain is wrong, can it be corrected?
The data in the database, yes. The fingerprint already recorded stays; the correction produces a new fingerprint, and the history shows both versions.
Does a blockchain make my product “certified”?
No. It proves the data hasn’t changed since it was recorded. Certification is issued by certification and inspection bodies.
Does putting only the hash on the blockchain make me GDPR-compliant?
Not on its own. According to the EDPB, the hash of personal data is still personal data, and an unkeyed hash is generally not enough [2]. The best choice is not to record personal data at all.
Do I need an account to verify?
On a public blockchain, no: anyone can consult the explorer.
How DPP helps
DPP stores only the fingerprint of batch and processing data on the DAC blockchain; the data itself stays in the database. Anyone can verify the fingerprint on a public explorer, and every change stays in the history with its author. See how it works on the technology page.
Sources
- NIST, FIPS 180-4 Secure Hash Standard
- EDPB, Guidelines 02/2025 on processing of personal data through blockchain technologies
- Regulation (EU) 2016/679 (GDPR), text on EUR-Lex
- Italian Decree-Law 135/2018, art. 8-ter (distributed ledger technologies), Normattiva
- Regulation (EU) 2024/1781 (ESPR), text on EUR-Lex