Blockchain timestamps are not eIDAS-qualified. Only a QTSP-issued RFC 3161 timestamp meets the legal presumption of eIDAS Articles 41 and 42. Here is exactly what that means for your documents in 2026.
In April 2025, a Munich patent attorney received a client with a software copyright dispute. The client had used a blockchain timestamping service to record a codebase hash on the Ethereum network six months earlier. The opposing party held an RFC 3161 timestamp from a Qualified Trust Service Provider. The hearing lasted forty minutes. The blockchain record was admitted as supporting evidence. The QTSP timestamp carried a legal presumption under eIDAS Art. 41. The client's lawyer knew within the first ten minutes how the afternoon would go.
No. Under eIDAS Art. 41-42, only timestamps issued by a Qualified Trust Service Provider (QTSP) using RFC 3161 carry a legal presumption of accuracy and date. Blockchain timestamps, whether Bitcoin, Ethereum, or any permissionless ledger, are not QTSP-certified and carry no Art. 41 legal presumption in EU or Swiss courts. They may serve as supporting evidence only.
Blockchain timestamping services marketed as legal proof tools have grown in popularity. Many claim to "prove" document existence on a specific date by recording a file hash on a public ledger. The claim is partly true and significantly misleading.
The hash is recorded. The block timestamp is real. But "recorded on a blockchain" is not the same as "legally presumed accurate under EU law." Those are two entirely different standards.
For EU businesses, Swiss companies operating under ZertES, and anyone whose documents may be used as evidence in EU or Swiss legal proceedings, the distinction is consequential.
eIDAS Art. 41 establishes that a qualified electronic timestamp shall enjoy a legal presumption of:
This presumption is legally reversible only if the challenger proves the QTSP's infrastructure was compromised, an extremely high bar that has essentially never been met in EU legal practice.
eIDAS Art. 42 sets the technical requirements for a qualified electronic timestamp:
A blockchain timestamp satisfies none of these four requirements. Blockchain consensus is not a QTSP. Block timestamps are not cryptographically bound to UTC in the sense required by RFC 3161. The block issuer is not on the EU Trust List.
| Criterion | Blockchain Timestamp | QTSP-Issued RFC 3161 Timestamp |
|---|---|---|
| Legal basis | None in EU/Swiss law | eIDAS Art. 41-42 / ZertES |
| Legal presumption of accuracy | No | Yes, challenger must disprove |
| Admissibility in EU/Swiss courts | Possible as supporting evidence | Legally presumed, no foundation required |
| Time source | Block consensus (not UTC-certified) | Authoritative UTC source, audited |
| RFC 3161 compliance | No | Yes |
| QTSP certification | No | Yes, EU Trust List |
| Court burden of proof | You must prove it | Opponent must disprove it |
| Acceptable for eIDAS Art. 42 | No | Yes |
| ZertES equivalent (Switzerland) | No | Yes (Swisscom Trust Services) |
The practical implication: if you present a blockchain timestamp in an EU or Swiss court as proof of document existence, you bear the full burden of establishing its accuracy and integrity. If you present a QTSP-issued timestamp, the law presumes it is correct. Your opponent must prove it is not.
Swiss Trust Layer issues timestamps via Swisscom Trust Services, simultaneously a ZertES-accredited certification authority and an eIDAS QTSP on the EU Trust List.
Every timestamp issued through Swiss Trust Layer:
No blockchain timestamp service provides these guarantees. The cryptographic mechanism is different, the issuing authority is different, and the legal status is categorically different.
Blockchain timestamps are not worthless. They are simply not eIDAS-qualified. In contexts where legal presumption is not required, such as private dispute resolution, informal proof between parties who agree on the mechanism, or supplementary documentation in a case where QTSP timestamps are also present, a blockchain record can be useful corroborating evidence.
The problem arises when blockchain timestamps are marketed as equivalent to QTSP-qualified timestamps, or when users rely on them exclusively for documents that may need to withstand legal scrutiny.
If your document might ever be used in litigation, regulatory compliance, IP enforcement, or due diligence by a sophisticated counterparty, use a QTSP-issued timestamp. The cost difference is negligible. The legal difference is significant.
Is a blockchain timestamp admissible as evidence in EU courts?
Generally yes, but as ordinary evidence that you must prove and authenticate. It has no legal presumption of accuracy under eIDAS. A QTSP-issued timestamp is legally presumed accurate without you needing to prove it.
Can I use a blockchain timestamp for eIDAS compliance?
No. eIDAS Art. 42 requires RFC 3161 compliance and a QTSP issuer. Blockchain timestamps satisfy neither requirement.
What is the difference between a timestamp and a qualified electronic timestamp?
A timestamp records a time and a data binding. A qualified electronic timestamp, as defined in eIDAS Art. 3(34), is one issued by a QTSP and meeting the Art. 42 technical requirements. Only the latter carries legal presumption.
Does Swiss Trust Layer use blockchain technology?
No. Swiss Trust Layer uses Swisscom Trust Services' RFC 3161-compliant timestamping infrastructure, an EU-listed QTSP and ZertES-accredited certification authority. This is the correct technical basis for legally presumed timestamps.
If I have both a blockchain timestamp and a QTSP timestamp, does the blockchain one add legal value?
Minimally. The QTSP timestamp is the legally operative one. The blockchain record may serve as a secondary corroborating data point, but it does not add legal presumption beyond what the QTSP timestamp already provides.
The Munich client's attorney understood this within the first ten minutes of the hearing. A blockchain hash on Ethereum costs fractions of a cent and carries no EU legal presumption. A QTSP-issued RFC 3161 timestamp carries a statutory presumption under eIDAS Art. 41 that the opposing party would need to disprove at their own cost. If you are sealing documents for IP protection, contract execution, copyright proof, or regulatory compliance in the EU or Switzerland, only a QTSP-issued RFC 3161 timestamp meets the eIDAS Art. 41 standard. Swiss Trust Layer provides exactly that: issued by Swisscom Trust Services, recognized across all 27 EU member states and Switzerland.
Seal your documents the legally correct way. Get started at swisstrustlayer.com.
See also: eIDAS Art. 41 explained: legal presumption in detail · eIDAS compliance overview · ZertES, Swiss legal framework
Protect your work with Swiss Trust Layer AG
Seal your intellectual property with a court-proof e-Seal backed by Swisscom Trust Services.
Book a Free Demo
A Backdated Term Sheet Is a 'Your Word Against Theirs' Problem. It Should Not Be.
Term sheets, LOIs, and early deal documents change hands fast during negotiation, across email, redlines, and verbal amendments. A dated, independently verifiable seal on the exact document ends the argument over what was agreed and when.
Your Government ID App Can Sign a Document. That Is Not Proof You Made It First.
The EU Digital Identity Wallet lets clients sign documents with a government ID. For fiduciaries, that only answers who signed, not when a specific draft or valuation existed. Here is why the difference matters in a dispute.
The Three-Year-Old File Problem: Proving Something You Made Years Ago Is Still Yours
Platforms shut down, metadata gets stripped by re-uploads, and formats fall out of use. A file that was easy to prove the week you made it can become nearly impossible to prove three years later.
"Poor Man's Copyright": Why Mailing Yourself a Sealed Envelope Doesn't Hold Up
Mailing yourself a sealed copy and relying on the postmark is one of the oldest pieces of copyright folklore. It relies on a physical envelope nobody independently checks, not a verifiable record.
Law Firms and Fiduciaries: Client Deliverables That Carry Their Own Evidence
Email trails and PDF metadata only prove what a firm says happened. A sealed deliverable carries its own hash, qualified timestamp, and verified identity, checkable without calling the firm.
