Blockchain timestamps under eIDAS: admissible, but not automatically “qualified”
Short answer: a blockchain timestamp is an electronic time stamp under eIDAS Article 41, so an EU court cannot reject it just for being electronic or non-qualified. It is not a qualified electronic time stamp unless a Qualified Trust Service Provider issues it — and that distinction changes the burden of proof, not the admissibility.
The short answer
No — a blockchain timestamp is not a qualified electronic time stamp under eIDAS, unless it is issued by a Qualified Trust Service Provider (QTSP) that meets Article 42. But it is an electronic time stamp, and under Article 41(1) it cannot be denied legal effect or admissibility as evidence in EU legal proceedings solely because it is electronic or non-qualified. The practical difference is not “valid vs invalid” — it is “admissible evidence” vs “admissible evidence that also carries a legal presumption.”
Two different things: “electronic” vs “qualified”
eIDAS (Regulation (EU) 910/2014, as amended by Regulation (EU) 2024/1183 — “eIDAS 2.0”) defines an electronic time stamp as data that binds other data to a particular time, establishing evidence that the data existed at that time (Art. 3(33)). A qualified electronic time stamp (Art. 3(34)) is the same thing, but issued under the stricter regime of Article 42 by a QTSP. Every qualified time stamp is an electronic time stamp; the reverse is not true.
What Article 41 actually says
- Art. 41(1): an electronic time stamp shall not be denied legal effect and admissibility as evidence in legal proceedings solely because it is in electronic form or does not meet the requirements of a qualified electronic time stamp.
- Art. 41(2): a qualified electronic time stamp enjoys the presumption of the accuracy of the date and time it indicates, and of the integrity of the data bound to that date and time.
- Art. 41(3): a qualified electronic time stamp issued in one EU Member State is recognised as qualified in all Member States.
What makes a time stamp “qualified” (Article 42)
- It binds the date and time to the data so as to reasonably preclude undetectable change of the data.
- It is based on an accurate time source linked to Coordinated Universal Time (UTC).
- It is issued using an advanced electronic signature or advanced electronic seal of a Qualified Trust Service Provider.
- The provider holds qualified status from an EU supervisory body and is listed on a national EU Trust List.
A public blockchain is not a QTSP and is not on an EU Trust List, so a raw blockchain timestamp does not meet Article 42 and does not receive the Article 41(2) presumption on its own. This is a factual statement about the regime, not a limitation unique to any one provider.
Where a blockchain timestamp lands
A blockchain timestamp is a non-qualified electronic time stamp: admissible across the EU under Art. 41(1), but without the automatic Art. 41(2) presumption. What it offers instead is demonstrable integrity rather than presumed integrity. A SHA-256 hash anchored on a public chain is time-bound by the consensus of thousands of independent nodes, the inclusion proof is mathematically verifiable, and any party — court, opponent, or expert — can check it against the public ledger without trusting the party that created it. In practice, that independent verifiability is often what a judge wants to see anyway.
So which do you need?
- You need a qualified electronic time stamp when a rule, contract, or regulator specifically requires “qualified” status, or when you want the Art. 41(2) legal presumption to shift the burden of proof onto the other side. That means an RFC 3161 timestamp from a QTSP on the EU Trust List.
- A blockchain timestamp fits when you need cheap, instant, high-volume proof that a file existed at a point in time — admissible across the EU and beyond — that anyone can verify independently and that outlives the issuer. IP and prior-art dates, contract drafts, AI-provenance, evidence preservation, internal records.
- The two are not mutually exclusive: for high-stakes matters some parties obtain both — a QTSP timestamp for the presumption and a blockchain anchor for independent, issuer-free verifiability.
How BA | Stamp fits
The SHA-256 hash is computed in your browser — the file itself never leaves your device. BA | Stamp aggregates the hash into a Merkle tree and anchors the root on Polygon (primary, low cost) and on Bitcoin via OpenTimestamps (long-term integrity). The output is a tamper-evident PDF certificate stating the document hash, the Merkle proof, the Polygon transaction, the Bitcoin block reference, and the eIDAS framing (Art. 41). It is a non-qualified electronic time stamp that anyone can verify against the public chains forever — even if BA | Stamp ceases to exist. Your first stamp is free, no wallet required.
Legal framework — Ireland
In compliance with the Irish Electronic Commerce Act 2000 s. 12–13 and eIDAS 2.0 Art. 41.
FAQ
Are blockchain timestamps qualified electronic timestamps under eIDAS?
No. A blockchain timestamp is a non-qualified electronic time stamp unless it is issued by a Qualified Trust Service Provider (QTSP) meeting Article 42 of eIDAS. It is still an electronic time stamp under Article 3(33) and is admissible as evidence under Article 41(1); it simply does not receive the Article 41(2) legal presumption reserved for qualified time stamps.
Are blockchain timestamps admissible as evidence in the EU?
Yes. Under eIDAS Article 41(1), an electronic time stamp cannot be denied legal effect or admissibility in legal proceedings solely because it is electronic or non-qualified. A blockchain timestamp is admissible across all EU Member States; what a non-qualified stamp lacks is the automatic presumption of accuracy, not admissibility.
Is a blockchain timestamp legally valid?
Yes, as a form of electronic evidence. eIDAS gives electronic time stamps legal effect and admissibility (Art. 41), and outside the EU frameworks such as FRE 902(13)-(14) in the US and Art. 2712 of the Italian Civil Code treat hash-anchored records as authenticable evidence. A blockchain timestamp proves a file existed at or before the anchoring time; it does not prove authorship or identity.
What is the difference between a qualified and a non-qualified electronic timestamp?
Both are admissible. A qualified electronic time stamp is issued by a QTSP on an EU Trust List under Article 42 and, under Article 41(2), is presumed accurate as to date/time and data integrity unless rebutted. A non-qualified electronic time stamp — including a blockchain timestamp — is admissible but does not carry that presumption; its reliability is shown on the evidence, which for a public-chain anchor is independently verifiable by anyone.
Do I need a QTSP for my timestamp to count?
Only if a rule, contract, or regulator specifically requires “qualified” status, or if you want the Article 41(2) presumption that shifts the burden of proof to the other side. For proof-of-existence that must be cheap, scalable, and independently verifiable without trusting the issuer, a blockchain timestamp is often sufficient — and some parties use both.
Can a blockchain timestamp be used to backdate a document?
No. A timestamp proves only that the data existed at the moment it was anchored — never earlier. This is inherent to every timestamping mechanism, qualified or not, including RFC 3161 QTSP timestamps.
Try your first stamp — free
No credit card. The certificate is admissible under the legal framework cited above.