Blockchain timestamp or qualified timestamp: what each proves, and where each fails

A qualified electronic timestamp and a blockchain anchor both prove that data existed at a point in time, but they derive their force from opposite places. One rests on an audited provider whose status is publicly recorded; the other rests on a public ledger that no party controls. Only the first carries a legal presumption.

Reference material on electronic evidence of existence and integrity. Last reviewed 18 August 2026.

Key points

A blockchain anchor does not carry the eIDAS Article 41 presumption. Article 42 requires a qualified provider’s signature or seal, which a public ledger has no way to supply.
Courts have still given blockchain timestamps real weight. Marseille, March 2025, accepted Bitcoin-anchored fingerprints as proof of copyright anteriority.
A block timestamp records inclusion in a block, not submission. The gap can be hours, so an anchor establishes an outer bound rather than a precise moment.
A qualified timestamp depends on institutional continuity; an anchor depends on none. Different failure modes, not different strengths.
Italy’s Article 8-ter is conditional on technical standards that have not been issued, so reports that Italy has granted blockchain timestamps eIDAS effect overstate the position.
Neither method establishes authorship. Both prove existence and integrity at a point in time, and nothing more.

On this page

Does a blockchain timestamp carry the eIDAS Article 41 presumption?
Have courts accepted blockchain timestamps as evidence?
What is the difference between what each method proves?
Why does the timing precision differ between them?
How do the two methods fail differently?
Is a blockchain timestamp legally recognised anywhere?
How have courts outside the EU treated blockchain evidence?
Which should I use for intellectual property evidence?
What does neither method prove?

Side by side

	Blockchain anchor	Qualified timestamp
What it attests	Data existed no later than a given block	Data existed at a stated moment
Timing precision	Outer bound; block inclusion may lag submission by hours	To the second, against a UTC-linked source
Legal presumption	None	Article 41, within the EU and EEA
Depends on	The network continuing, and the hash function holding	The provider’s certificate remaining checkable and the trusted list
Verified by	Anyone, from the public ledger	Anyone, from the token and the trusted list
Proves authorship	No	No

Does a blockchain timestamp carry the eIDAS Article 41 presumption?

No. The Article 41 presumption applies to qualified electronic timestamps, which under Article 42 must be issued by a qualified trust service provider and signed with that provider’s advanced electronic signature or seal. A public blockchain has no provider to sign anything, so the requirement cannot be met by anchoring alone.

That is a real limitation and worth stating plainly. Anyone claiming a blockchain anchor gives you a presumption of accuracy under eIDAS is overstating the position.

It does not follow that a blockchain anchor has no evidential value. Admissibility and weight are separate questions from presumption, and courts have addressed them directly.

Have courts accepted blockchain timestamps as evidence?

Yes. In March 2025 the Tribunal judiciaire de Marseille found that cryptographic fingerprints anchored on the Bitcoin blockchain constituted sufficient proof of a claimant’s copyright in a fashion design dispute. The court accorded full probative weight to the blockchain timestamp reports, notwithstanding that the related seizure report had been annulled for procedural irregularity. The case is reported by the EUIPO as RG 23/00046.

Two caveats matter. It is a first-instance decision rather than binding precedent, and the blockchain evidence was treated as part of a body of consistent evidence rather than standing alone. The court also had a bailiff’s verification report and evidence of public disclosure before it.

The useful reading is not that a blockchain anchor is conclusive, but that a European court has been willing to give it real weight in exactly the kind of dispute creators face.

What is the difference between what each method proves?

A qualified electronic timestamp proves that specific data existed at a specific moment, attested by an audited provider whose status is recorded on an EU trusted list, and shifts the burden of proof to whoever disputes it.

A blockchain anchor proves that specific data existed no later than a particular block, attested by a public record that no single party controls and that can be checked by anyone without contacting anybody.

The distinction is not that one is stronger. It is that one derives its force from an accountable institution and the other from the absence of any institution at all.

Why does the timing precision differ between them?

This is the practical distinction most comparisons miss. A blockchain timestamp reflects when a transaction was included in a block, not when it was submitted, and that gap can run from seconds to several hours.

A qualified timestamp records the moment the request reached the provider, against a time source linked to Coordinated Universal Time. The precision is to the second and it is attested.

So a blockchain anchor establishes an outer bound: the data existed no later than this block. Where the exact moment matters — a filing deadline, a disclosure window, competing claims of priority hours apart — that bound may not be tight enough on its own.

How do the two methods fail differently?

A qualified timestamp depends on institutional continuity. Verification requires the provider’s signing certificate to remain checkable and the trusted list to continue recording what its status was at the time of stamping. Those are well-maintained systems, but they are systems that somebody has to keep running.

A blockchain anchor depends on the network continuing to exist and on the hash function remaining sound. It depends on no company, no supervisory body and no certificate.

Neither failure mode is likely in any near horizon. But they are different failure modes, which is the reason for not choosing between them where the evidence is expected to matter over long periods.

Is a blockchain timestamp legally recognised anywhere?

Italy is the case usually cited, and it is more equivocal than commonly reported. Article 8-ter of Decree-Law 135/2018, converted by Law 12/2019, provides that storing a computer document using distributed ledger technologies produces the legal effects of the electronic time validation referred to in Article 41 of Regulation (EU) 910/2014.

The same article makes that effect conditional on the Agency for Digital Italy identifying the technical standards a distributed ledger must meet. That implementing regulation has not been issued. The provision exists; the mechanism that would make it operative does not.

Statements that Italy has granted blockchain timestamps eIDAS legal effect should be read with that in mind.

How have courts outside the EU treated blockchain evidence?

In China, the Hangzhou Internet Court ruled in 2018 that evidence stored on a blockchain was admissible where the underlying technical process could be shown to be reliable.

In the United States, the District Court for the District of Columbia accepted blockchain records as reliable evidence under the Daubert standard in United States v. Sterlingov. A separate line of authority holds that purely machine-generated data is not hearsay because there is no human declarant, which bears directly on records written to a ledger without human intervention.

In England and Wales, the Civil Evidence Act 1995 removed the general prohibition on hearsay in civil proceedings, so the question is weight rather than admissibility. The UK Jurisdiction Taskforce’s 2019 Legal Statement confirmed that distributed ledger records can constitute reliable evidence.

Which should I use for intellectual property evidence?

If the dispute is likely to be heard in an EU member state and the date is the contested issue, the Article 41 presumption is a material advantage. Making the other side prove the timestamp wrong is a substantially better position than having to prove it right.

If the evidence may need to hold for many years, or may be relied on somewhere the eIDAS framework does not reach, an anchor that depends on no institution has its own value.

For most creative and technical work the honest answer is that the question is not which to choose. The anchor establishes a public, institution-independent record; the qualified timestamp adds precision and the presumption where it applies.

What does neither method prove?

Neither establishes authorship. Both establish that particular data existed in a particular form at a particular time and has not changed since. Nothing in either mechanism identifies who created the data or who submitted it.

The Marseille court did not treat the blockchain records as proof of authorship standing alone. It weighed them alongside evidence of public disclosure and a bailiff’s report as a consistent body of evidence.

Anyone building an evidential position should expect to combine a timestamp with other material: version history, correspondence, drafts, witness evidence. A timestamp is corroboration of when, not proof of who.