Blockchain vs qualified vs RFC 3161 timestamps

An RFC 3161 timestamp is signed by a time-stamping authority; an eIDAS qualified time stamp is an RFC 3161-type stamp from a supervised EU provider and is presumed accurate in the EU; a blockchain timestamp writes a hash to a public ledger. All prove a file existed at a time; only qualified stamps carry the EU legal presumption.

The three types

Blockchain timestampRFC 3161 trusted timestampeIDAS qualified time stamp
Who vouches for the timePublic blockchain networkTime-stamping authority (TSA)Qualified trust service provider (EU-supervised)
What you getTransaction / certificateSigned token (.tsr)Signed token, qualified
Depends on one companyNo for the record itselfYes (the TSA's key)Yes, but supervised
EU legal presumptionNoNoYes (eIDAS Art. 41(2))
Admissible as evidence (EU)Yes, weighed freely (Art. 41(1))Yes, weighed freelyYes, presumed accurate
Typical costFree–lowFree–low (e.g. FreeTSA)Paid per stamp

When to use which

  • Creative work, drafts, everyday files: blockchain timestamp — free and unlimited with SecureAuthor.
  • Software signing, technical archives: RFC 3161 TSA.
  • Contracts and evidence for EU courts or authorities: qualified time stamp, possibly in addition to a blockchain record.

Frequently asked questions

Is a blockchain timestamp eIDAS-qualified?

Not by itself. Qualified time stamps must come from a qualified trust service provider on the EU Trusted List.

Does a non-qualified timestamp count in the EU?

Yes, as evidence. Under eIDAS Article 41(1) an electronic time stamp cannot be denied legal effect or admissibility solely because it is electronic or not qualified.

Which should I use?

For everyday creative work, a free blockchain timestamp. For contracts or evidence in EU proceedings where a presumption matters, add a qualified time stamp.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file