Are blockchain timestamps qualified under eIDAS? No. Here is what they are worth instead

The short answer

No. A timestamp written into Bitcoin, Ethereum or any other public blockchain is not a qualified electronic time stamp under the eIDAS Regulation (EU) No 910/2014. Qualified status is not a property of a technology. It is a legal status that only a qualified trust service provider (QTSP), supervised in an EU Member State and listed on that State's trusted list, can confer by issuing a time stamp that meets Article 42.

That does not make blockchain timestamps worthless. Article 41(1) says an electronic time stamp cannot be denied legal effect or admissibility as evidence solely because it is electronic or not qualified. The difference lies in the burden of proof: a qualified time stamp comes with a legal presumption of accuracy and integrity under Article 41(2), while a blockchain timestamp has to be explained and defended by whoever relies on it.

What makes a time stamp qualified under eIDAS

Article 3(34) defines a qualified electronic time stamp as one that meets the requirements of Article 42. In practice that means four things:

• It binds the date and time to the data in a way that reasonably precludes the data being changed undetectably.
• It is based on an accurate time source linked to Coordinated Universal Time (UTC).
• It is signed with an advanced electronic signature or sealed with an advanced electronic seal of the qualified trust service provider, or by an equivalent method.
• It is issued by a provider that holds qualified status for this service, which anyone can check on the EU Trusted List.

The last point is the one a public blockchain cannot meet. Bitcoin has no operator that is supervised, audited and granted qualified status. A miner is not a trust service provider, and the block time is not signed by anyone who is accountable for it.

Where blockchain timestamps fit: Article 41(1)

eIDAS deliberately does not exclude non-qualified time stamps. Under Article 41(1) a court may not reject one only because it is electronic or not qualified. It weighs it like any other evidence, under its own national procedural rules.

What changes is who has to prove what. With a qualified time stamp, the other side has to rebut the presumption that the date, the time and the integrity of the data are correct. With a blockchain timestamp, you have to show the court how the proof works, why it is reliable and that the hash really corresponds to your file. That usually needs an expert explanation, and the opponent can attack every link of the chain.

What a blockchain timestamp proves, and what it does not

Anchoring a SHA-256 hash in a public blockchain is a strong technical fact, but a narrow one. Read it precisely:

• It proves that data with exactly this hash existed no later than the block in which the hash, or a Merkle root containing it, was recorded.
• It does not prove an exact time. A Bitcoin block time is set by the miner within protocol tolerances, and aggregation services such as OpenTimestamps batch many hashes, so confirmation takes hours.
• It does not prove who created the content, where it came from or what a web page looked like. The hash of a manipulated screenshot is anchored just as well as the hash of a genuine capture.
• It does not depend on any company surviving. Anyone can verify the anchor against the public chain years later, and that is its real strength.

eIDAS 2.0: qualified electronic ledgers

The 2024 revision of eIDAS, Regulation (EU) 2024/1183, added electronic ledgers as a new trust service. Article 45k repeats the non-discrimination rule for ledgers and gives data records in a qualified electronic ledger a presumption of their unique and accurate sequential chronological ordering and of their integrity.

The key word is again qualified. Under Article 45l a qualified electronic ledger must be created and managed by one or more qualified trust service providers, must establish the origin of data records and must make any later change immediately detectable. Commission Implementing Regulation (EU) 2025/2531, in force since January 2026, sets the reference standards, including signatures or seals based on qualified certificates and certified devices for the signing keys.

So eIDAS 2.0 does not turn Bitcoin into a qualified ledger. It creates a route for supervised ledger services to earn qualified status. Before relying on one, check the EU Trusted List for the provider and for that specific qualified service.

National rules: the Italian example

A few Member States went further on their own. Italy's Decree-Law No 135/2018, Article 8-ter, provides that storing a document by means of distributed ledger technology produces the legal effects of an electronic time stamp under Article 41 eIDAS, subject to technical standards set by the Italian digital agency AgID. Note the wording: the effects of an electronic time stamp, not of a qualified one. A national rule like this can help inside one country, but it does not create EU-wide qualified status.

In practice: how to use both in a dispute

For lawyers, court experts and compliance teams the practical answer is not either-or. Use each layer for what it does best:

• Obtain a qualified electronic time stamp from a QTSP over the hashes of everything you captured. That is what triggers the Article 41(2) presumption.
• Add a blockchain anchor as an independent witness that the record existed by a given block, verifiable without any provider.
• Keep the full package: the original files, a manifest with SHA-256 values, the RFC 3161 time-stamp token and the certificate chain of the time-stamping authority.
• Store a snapshot of the QTSP's status on the EU Trusted List at the time of stamping, so verification still works if the list changes later.
• Document the method: who captured what, with which tool, from which URL and in which order.

A timestamp only covers what was hashed. If the capture itself is a plain screenshot, the best timestamp in the world proves only that this screenshot existed. Courts look at the whole chain, from acquisition to verification.

How GetProofAnchor combines the two

GetProofAnchor seals every proof with an eIDAS qualified time stamp from SK ID Solutions, a QTSP on the EU Trusted List, over a payload that binds the hashes of all artifacts: full-page screenshot, HTML, MHTML, video, HAR, TLS certificate chain, DNS and WHOIS data. In addition, the hash chain of all proofs is anchored in Bitcoin through OpenTimestamps in batches, so the record can be checked against the public blockchain without trusting us.

The Evidence ZIP contains the time-stamp token and a snapshot of the EU Trusted List, and the open-source gpa-verify tool checks it offline. You can start with a 9 EUR pack of three proofs, use the Forensic Browser desktop app for multi-page sessions with a PAdES PDF that validates in Adobe Acrobat Reader, or order Assisted Capture from 49 EUR if you want us to capture the pages for you. Whether evidence is admitted and how much weight it carries is always for the court to decide.

FAQ

Sources

• Regulation (EU) No 910/2014 (eIDAS), Articles 3, 41 and 42 – EUR-Lex
• Regulation (EU) 2024/1183 (eIDAS 2.0), Articles 45k and 45l – EUR-Lex
• Commission Implementing Regulation (EU) 2025/2531 on qualified electronic ledgers – EUR-Lex
• EU Trusted List browser – European Commission
• Italy: Decree-Law No 135/2018, Article 8-ter – Normattiva
• OpenTimestamps – project website