Are Blockchain Timestamps Qualified Electronic Timestamps Under eIDAS? (2026)

In April 2025, a Munich fintech startup's CTO pointed to an OpenTimestamps Bitcoin anchor as proof the company's payment routing algorithm predated a competitor's patent filing. The competitor's legal team cited eIDAS Art. 42. The Bitcoin anchor carried no QTSP accreditation, no Art. 41 legal presumption, and no UTC binding traceable to a recognised source. The startup spent six months and EUR 180,000 defending a patent priority dispute that a qualified timestamp would have resolved at the filing date.

No. Blockchain timestamps are not qualified electronic timestamps under eIDAS Art. 42. That article requires timestamps to be issued by an EU-listed Qualified Trust Service Provider (QTSP), cryptographically bound to a UTC time source, and linked to data via a qualified electronic signature or seal. Public blockchains meet none of these three criteria and carry no Art. 41 legal presumption of accuracy in EU or Swiss courts.

Blockchain timestamps are not qualified electronic timestamps under eIDAS Regulation (EU) No 910/2014. eIDAS Art. 42 requires timestamps to be issued by an EU-listed Qualified Trust Service Provider (QTSP), cryptographically bound to a UTC time source, and capable of detecting backdating. Public blockchains hold none of these accreditations and carry no legal presumption of accuracy across EU member states.

What Is an eIDAS Qualified Electronic Timestamp?

Under eIDAS Art. 41, a qualified electronic timestamp enjoys a legal presumption of accuracy as to the date and time it indicates, and as to the integrity of the data to which it is bound. This presumption is recognised in every EU member state without further proof.

To earn that presumption, eIDAS Art. 42 sets four hard requirements:

1. The data is bound to the date and time in a manner that precludes undetectable alteration.
2. The date and time is based on a coordinated universal time (UTC) source.
3. The timestamp is issued by a Qualified Trust Service Provider (QTSP) named on an EU national trust list (EUTL).
4. The timestamp is linked to the data using an advanced or qualified electronic signature or seal of the issuing QTSP.

QTSPs are audited and supervised by national authorities, such as the Bundesnetzagentur in Germany and ANSSI in France. Their inclusion on a national trust list is what turns a cryptographic assertion into a legally presumed fact under EU law. You can verify QTSP status on our eIDAS compliance overview.

What Is a Blockchain Timestamp?

A blockchain timestamp is a record written to a distributed ledger, most commonly Bitcoin, Ethereum, or a permissioned chain, at the moment a transaction is confirmed. The block header includes a Unix epoch value set by the miner or validator at the time of block creation.

Blockchain timestamps offer genuine technical properties: immutability once confirmed, distributed verification, and a permanent public record. Projects such as OpenTimestamps use Bitcoin's block headers to anchor document hashes, providing a tamper-evident audit trail.

For many informal use cases, such as proving you possessed a document on a given day, creating an internal audit trail, or establishing a creative timeline, a blockchain timestamp is a useful tool. What it is not is a qualified electronic timestamp under EU law.

Why Blockchain Timestamps Do Not Qualify Under eIDAS (Art. 42)

Three structural gaps prevent any public blockchain from satisfying eIDAS Art. 42:

No QTSP accreditation. Bitcoin miners, Ethereum validators, and permissioned-chain operators are not listed on any EU national trust list. No supervisory authority audits them for timestamp accuracy. Without that listing, the Art. 41 legal presumption simply does not attach.

No guaranteed UTC binding. Block timestamps are set by miners within a tolerance window. Bitcoin's protocol allows a block timestamp to be up to two hours in the past or future relative to network median time. A court cannot presume accuracy from a value the protocol itself tolerates varying by hours.

No issuing QTSP signature. Art. 42(b) requires the timestamp to be linked to data using an advanced or qualified electronic signature of the issuing QTSP. A miner broadcasting a block is not signing anything in the eIDAS sense. There is no qualified certificate, no QTSP key pair, and no supervisory chain of trust.

Dimension	Blockchain Timestamp	eIDAS Qualified Timestamp
Legal status	No EU legal presumption	Art. 41 presumption, admissible in all EU courts
QTSP accreditation	None: miners/validators are not QTSPs	Mandatory: issuer must appear on EU national trust list
Court admissibility	Case-by-case; disputed in cross-border proceedings	Automatic across all 27 EU member states
Presumption of accuracy	None: must be argued from technical evidence	Statutory: opponent must rebut with evidence

Technical Requirements: Why Blockchain Cannot Meet eIDAS Art. 42

Requirement 1: QTSP Issuer Accreditation (Art. 42(1)(a))

eIDAS Art. 42(1)(a) requires that a qualified electronic timestamp be issued by a Qualified Trust Service Provider (QTSP) listed on an EU Member State Trusted List (EUTL). The EUTL is maintained by the European Commission at https://eidas.ec.europa.eu/efda/tl-browser/ and contains only nationally-supervised TSAs that have passed conformity assessment by an accredited body.

Blockchain protocols, including Bitcoin, Ethereum, or any permissionless ledger, have no issuing authority. There is no legal entity that can be listed on the EUTL for a decentralised network. The timestamp embedded in a block header is set by the mining node and carries no supervisory accountability. Better cryptography would not fix this. eIDAS Art. 42 creates a structural exclusion because it is about institutional trust, not algorithmic proof.

Requirement 2: RFC 3161 Timestamp Token Format (Art. 42(1)(b))

Art. 42(1)(b) requires the timestamp to be bound to the data using a qualified electronic signature or seal from the issuing QTSP. In practice, this means the QTSP produces an RFC 3161 TSTInfo structure, a DER-encoded ASN.1 object containing the MessageImprint (SHA-256 hash of your document), the genTime (UTC time), and the TSA's digital signature over both fields.

A blockchain hash is a 32-byte hex string appended to a block. It carries no issuer signature, no binding to a legal entity, and no cryptographic proof of what time the data existed. It only proves that the data was included in a block. It does not prove when it existed, who confirmed it, or under whose legal responsibility.

Requirement 3: Trusted UTC Time Source (Art. 42(1)(c))

Art. 42(1)(c) requires the time to be bound to a Coordinated Universal Time (UTC) source traceable to the BIPM International Bureau of Weights and Measures. Accredited TSAs use atomic clocks with sub-second UTC accuracy, audited against primary time standards.

Bitcoin block timestamps carry a tolerance of plus or minus 2 hours. The Bitcoin protocol only requires that a block timestamp be greater than the median of the previous 11 blocks and within 2 hours of network-adjusted time, a 7,200-second window that is forensically unacceptable for legal proceedings where the precise moment of creation matters.

What a Qualified Timestamp Would Have Changed

If the Munich startup's CTO had anchored the algorithm's source code hash with a QTSP-issued qualified timestamp before the patent filing date, the document would have carried an Art. 41 legal presumption of accuracy across all 27 EU member states. The competitor's legal team would have faced the burden of disproving that presumption, not the startup the burden of explaining why a Bitcoin block timestamp carries no supervisory chain of trust. The entire six-month proceeding would have collapsed at the first procedural hearing.

The Legal Consequences: Court Admissibility

The Art. 41 presumption is not a procedural technicality. It shifts the burden of proof. When you present a qualified timestamp in an EU court, the opposing party must demonstrate that the timestamp is inaccurate or that the data has been altered. Without a qualified timestamp, you carry the full burden of proving when your document existed.

For IP disputes, copyright claims, trade secret cases, and contract formation disputes, that burden shift is decisive. A blockchain record may be admitted as evidence in some jurisdictions, but it will be contested: opposing counsel will challenge the miner's timestamp tolerance, the absence of a supervisory chain, and the lack of a qualified certificate. A QTSP-issued timestamp cannot be challenged on those grounds.

For more on how eIDAS timestamps compare to Swiss ZertES qualified timestamps, see our eIDAS vs ZertES comparison.

What This Means for IP Owners and Businesses

If your primary need is an internal audit trail or a low-cost existence proof for non-litigious purposes, a blockchain anchor may be sufficient. But if you anticipate any of the following scenarios, only a qualified timestamp provides the legal certainty you need:

• Copyright disputes: proving you created a work before a competitor
• Patent priority: documenting conception or reduction to practice
• Trade secret protection: establishing that information was confidential at a specific date
• Contract formation: proving the exact moment terms were agreed
• Regulatory compliance: meeting eIDAS or sector-specific requirements for timestamped records

For businesses operating under eIDAS compliance obligations, using blockchain timestamps where qualified timestamps are required carries legal risk and may constitute non-compliance.

For more detail on the technical and legal structure of qualified timestamps, see our guide to eIDAS-qualified timestamps explained.

How Swiss Trust Layer Provides eIDAS-Qualified Timestamps

Swiss Trust Layer operates as a QTSP-backed platform. Every document sealed through our service receives a qualified electronic timestamp issued by an accredited trust service provider, cryptographically bound to a UTC time source and linked to your document hash via a qualified electronic seal.

The result is a PAdES-compliant sealed document that carries the full Art. 41 legal presumption, admissible in any EU member state court without further argument about accuracy or integrity.

You do not need to understand the underlying PKI infrastructure. You upload your document, we apply the qualified timestamp and digital seal, and you receive a certificate that any EU court, regulator, or counterparty can verify independently, without creating an account or contacting us.

CHF 5 vs EUR 180,000

The Munich startup settled the patent challenge, absorbing EUR 180,000 in legal costs, with no damages recovered for six months of diverted engineering time. A QTSP-issued qualified timestamp at the time of development would have cost CHF 5 per document. The Art. 41 presumption that document would have carried is the same presumption a six-month legal battle failed to establish through a Bitcoin block header.

Get a Court-Admissible Qualified Timestamp