Is a blockchain timestamp valid in court?

The short answer

Yes, as evidence — in most places as ordinary evidence whose weight the court decides, and in a few jurisdictions with explicit statutory or judicial backing.

No jurisdiction treats a blockchain timestamp as conclusive on its own. What courts have accepted is narrower and more useful than that: the record reliably shows that a specific file existed by a specific time and has not changed since. Whether that fact wins your case depends on everything else in the record.

Anyone who tells you a timestamp is "court-proof" or "legally binding" is overselling. Anyone who tells you it is worthless has not read the last two years of decisions.

Admissibility and weight are two different questions

Almost every argument about blockchain evidence confuses these.

Admissibility asks whether the court will look at the evidence at all. This is largely a technical question about authentication — can you show the record is what you say it is? Blockchain timestamps do unusually well here, because the verification is reproducible by anyone.

Weight asks how much the court should believe it, and what it proves. This is where the real limits sit. A timestamp is strong on one narrow point (this file existed by this date, unaltered) and silent on everything else.

A timestamp that is admitted and then given its correct, narrow weight is doing exactly its job.

Jurisdiction by jurisdiction

France — the first clear judgment

On 20 March 2025, the Tribunal Judiciaire de Marseille decided a counterfeiting dispute between AZ Factory and a Chinese company over pyjamas derived from sketches by the designer Alber Elbaz.

AZ Factory produced a blockchain anchoring certificate containing the SHA-256 hash of its creation files, anchored on a public blockchain in May and September 2021 — months before the disputed collection appeared. The court accepted the timestamp as establishing anteriority, and treated it as contributing to establishing ownership of the copyright.

This is the decision to cite, and it is worth being precise about why. It is not that a French court declared blockchain timestamps legally special. It is that a claimant produced a reproducible cryptographic record of what it held and when, the record was checkable, and the court gave it the weight such a record deserves. That is how documentary evidence is supposed to work.

Note also what carried it: the sketches were timestamped before the dispute existed, not afterwards. A timestamp created after a conflict begins proves far less.

European Union — eIDAS Article 41

The eIDAS Regulation distinguishes qualified electronic timestamps from everything else.

A qualified timestamp is issued by a qualified trust service provider under audit, and Article 41(2) gives it a legal presumption of the accuracy of its date and the integrity of the data. That presumption is the thing law firms care about.

A blockchain timestamp is not a qualified timestamp. But Article 41(1) is equally important: an electronic timestamp shall not be denied legal effect or admissibility as evidence solely because it is in electronic form or does not meet the qualified requirements.

So in the EU the position is: admissible, no presumption, weight assessed on the merits. That is a perfectly workable place to be, and it is where most evidence lives.

We are not a qualified trust service provider and we do not claim to be. If someone has specifically asked you for a qualified timestamp, you need a qualified TSA — see the Bernstein comparison, which pairs both.

Italy — the law that is on the books but not in force

Italy went furthest on paper. Article 8-ter of Law 12/2019 provides that storing a computerised document using distributed ledger technologies produces the legal effects of an electronic timestamp under eIDAS.

The catch is real and frequently omitted: the article delegates the technical standards to AgID, the Agency for Digital Italy, and those standards have not been issued. Without them the provision is widely regarded as unimplemented, so the practical effect is far weaker than the headline suggests.

Cite it as evidence of legislative direction. Do not cite it as a settled rule you can rely on.

China — the most developed body of practice

China has gone furthest in practice rather than in theory.

The Supreme People's Court's September 2018 Provisions on Several Issues Concerning the Trial of Cases by Internet Courts, Article 11(2), state that where electronic data is collected through electronic signature, trusted timestamping, hash verification, blockchain or similar methods, and its authenticity can be verified, the Internet Court shall confirm that authenticity. This followed the Hangzhou Internet Court's earlier acceptance of blockchain evidence and extended it to the Beijing and Guangzhou Internet Courts.

The Online Litigation Rules issued on 16 June 2021 and effective 1 August 2021 apply to over three thousand courts and set out how authenticity of blockchain evidence is reviewed.

If you want to see what a mature legal treatment of this evidence looks like, China is where to look.

United States — no special rule, and none needed

There is no blockchain provision in the Federal Rules of Evidence, and that is not a gap.

• FRE 901(b)(9) allows authentication by evidence describing a process or system and showing it produces an accurate result. A hash function plus a public ledger is exactly such a process.
• FRE 902(13) provides for self-authentication of records generated by an electronic process, with a qualified person's certification.
• FRE 902(14) provides for self-authentication of data copied from an electronic device, authenticated by hash value — the rule explicitly contemplates hash-based identification.

In practice you would expect to authenticate a blockchain timestamp through testimony or certification explaining the hashing and the ledger, and then argue weight. State courts vary; a handful of states have passed blockchain-specific evidence or records legislation.

What still defeats a timestamp

Being realistic here is more useful than being encouraging.

It does not prove authorship. This is the big one. A timestamp proves you had the file, not that you made it. Someone who copies your work and timestamps it gets an honest record that they had a copy on that date. See proof of existence vs proof of authorship.

A later timestamp loses to an earlier one. If the other side timestamped first, your record is the weaker one. This is why timestamping the earliest draft matters far more than timestamping the final version.

Post-dispute timestamps are heavily discounted. A record created after the conflict started tells a court very little, and may invite the inference that it was created for the litigation.

The file has to be produced. A timestamp commits to a hash. To use it you must produce the original file and demonstrate that it hashes to the same value. Lose the file and the timestamp proves that something existed, and nothing more.

Nobody has to know what a Merkle tree is. Evidence you cannot explain is evidence you cannot use. If verification requires proprietary software or a proof file only you can interpret, expect friction. A record readable directly from a public block explorer avoids most of it.

How to make a timestamp as strong as it can be

1. Timestamp early, and timestamp drafts. Priority is the thing you are establishing. The earliest artefact is the most valuable one.
2. Timestamp iterations, not just the final file. A sequence of dated versions tells a story of creation. One dated file tells a story of possession.
3. Keep the original files, byte-for-byte. Re-saving a document changes its bytes and breaks the hash. Archive the exact file.
4. Record what the file was. Our certificates carry a free-text field — use it for the author name, the project, the version. It is hashed together with the file's fingerprint, so it is fixed at the same moment.
5. Keep the ordinary evidence too. Source files, project histories, emails, drafts, commits. The timestamp anchors the date; the rest establishes that you made it.
6. Prefer a record that verifies without the vendor. If the company that issued your proof has to still exist for the proof to work, that is a dependency worth removing. Ours is one Ethereum transaction whose contents anyone can read on Etherscan — see how to verify a timestamp.

The honest summary

A blockchain timestamp is good evidence of one narrow, valuable fact, and courts are increasingly comfortable with it. It is not a registration, not a right, and not a substitute for legal advice about your specific situation. Used for what it is — a cheap, permanent, independently checkable anchor on a date — it is one of the better pieces of evidence you can create in thirty seconds.

This page describes publicly reported decisions and legislation as of August 2026. It is general information, not legal advice, and outcomes turn on the facts of each case. Take advice on anything that matters.