Proof of Existence vs a Timestamp Authority: which trust model do you need?

A Timestamp Authority and a Proof of Existence answer the same question — did this data exist by this time? — but they root the answer in different places. A Timestamp Authority gives you a time token signed by a named, trusted provider. A Label 309 Proof of Existence (PoE) gives you a public record on Cardano that anyone can verify from the blockchain and the original bytes, without asking the publisher or any single timestamping service.

That is the whole decision in one line: a Timestamp Authority asks you to trust a specific authority and its certificate chain; Label 309 asks you to trust public Cardano consensus. Both are legitimate. Which one fits depends on what your workflow has to satisfy. Some regulated processes specifically require a qualified timestamp. Many product, audit, engineering, and public-proof workflows are better served by an open proof that any party can check, with no service to outlive.

What is a Timestamp Authority?

A Timestamp Authority (TSA) is a trusted service that issues signed timestamp tokens.

The common technical standard is RFC 3161, the Time-Stamp Protocol. A requester sends a hash of the data to the TSA. The TSA returns a token containing the message imprint, a time, a serial number, policy information, and other fields, signed with the TSA's private key. To verify, you check that signature and the TSA's certificate chain.

The TSA never sees the document — it sees only the digest. But the trust story depends entirely on the authority: its signing key, its time source, its operating policy, its certificate, and any legal framework that recognizes it. The proof is only as good as that named provider remains.

That is exactly the right model when a process requires a recognized third-party time service.

What is a Label 309 Proof of Existence?

Label 309 is an open, vendor-neutral standard for Proof of Existence records on Cardano. It has been submitted to the Cardano CIP process and is under review by the CIP editors as a Metadata-category proposal.

At its simplest, a Label 309 record publishes a content hash in Cardano transaction metadata under metadata label 309. The block time of that transaction becomes the public time witness. To verify, anyone fetches the transaction from a Cardano explorer, validates the record format, recomputes the hash from the original bytes, and checks that it matches. The publisher is never contacted.

A Label 309 record can also carry more than a bare hash: optional authorship signatures, references to sealed encrypted payloads, recipient key slots, Merkle roots that commit to large off-chain lists, and a pointer to a record it supersedes. None of that fits the classic "ask a timestamping server for a token" picture — which is part of the point.

What is the core difference?

A TSA is an institutional trust model.

You trust that a specific service was authorized, ran correctly, used a reliable clock, protected its signing key, followed its stated policy, and issued a valid token. Verification leans on that authority and its public-key infrastructure (PKI).

Label 309 is a public-record trust model.

You trust the public Cardano chain for inclusion and block time, the hash function for content binding, and the verifier for correct validation. You do not need to trust CardanoWall, the publisher's server, or any single issuing authority to check the basic proof. A verifier needs only the transaction reference, optionally the content bytes, and a public Cardano explorer.

So the question is not "which one is universally better?" It is:

Which trust model does this workflow need?

When should you use a Timestamp Authority?

Use a TSA when the workflow calls for one. That typically includes:

contracts that name a specific timestamping provider;
electronic-signature systems built around X.509 certificates;
regulated processes that require a qualified trust service;
jurisdictions where qualified timestamps carry specific legal presumptions;
PDF signing and long-term validation (LTV) workflows;
enterprise document processes already built on PKI.

In the European Union, the eIDAS Regulation gives qualified electronic timestamps a specific legal status. Article 41(1) says an electronic timestamp shall not be denied legal effect solely because it is in electronic form, and Article 41(2) gives a qualified electronic timestamp a presumption of the accuracy of its date and time and of the integrity of the data it is attached to. That presumption shifts the burden onto whoever disputes the timestamp — though it does not make any timestamp automatically decisive in every case. It is a strong, jurisdiction-specific reason to use qualified services where they apply.

If a lawyer, regulator, procurement rule, or standard says "qualified timestamp," use the qualified timestamp.

When should you use Label 309?

Use Label 309 when you want a public, independently verifiable proof that does not depend on a single timestamping provider. It fits workflows like:

proving a file, dataset, or manifest existed by a public time;
anchoring AI content-generation manifests;
committing CI/CD release evidence;
publishing the root of a compliance log;
preserving sealed files for yourself or specific recipients;
committing thousands of hashes through a single Merkle root;
building a product or API around open proof records;
letting third parties verify records without your service in the loop.

The practical advantage is portability. The proof is just a Cardano transaction and the bytes it commits to. If CardanoWall — or whoever published the record — disappears, the proof still verifies from the chain and the original content. There is no certificate to renew and no authority whose shutdown invalidates anything. For the foundations, start with what Proof of Existence is.

Which one is better for legal evidence?

It depends on the legal question, and you should treat the rest of this section as a system-design distinction, not legal advice.

A qualified timestamp can carry statutory or contractual weight that a blockchain proof does not automatically have. That matters in regulated document signing, cross-border trust services, and formal electronic-signature workflows — the eIDAS presumption above is a concrete example.

A Label 309 proof can still be strong evidence of timing and integrity, especially when the goal is to show a public commitment the publisher did not control. It can also commit to structures a TSA token never tries to model: sealed payloads, recipient delivery, Merkle batches, and application-specific manifests. What it does not do — and neither does a TSA token — is prove that the content is true, that you own it, that you authored it, or that you hold any rights to it. A proof of existence is a claim about timing and integrity, nothing more.

For high-stakes use, ask counsel which evidence package fits your jurisdiction and process.

Can you use both?

Yes — and for important records, that is often the sensible answer:

Hash the file or manifest.
Obtain an RFC 3161 or qualified timestamp token, if the workflow needs one.
Put the timestamp token, the file hash, and the related evidence into a manifest.
Publish a Label 309 proof for that manifest, or for a Merkle root over the whole evidence set.

Now the record has two independent timing layers:

an institutional timestamp from a recognized TSA;
a public blockchain anchor under an open proof format.

The two answer the same broad timing question from different trust roots, so a weakness in either layer does not collapse the other.

What does a Timestamp Authority not prove?

A TSA token does not prove the content is true. It does not prove ownership. It does not preserve the original file unless your own system stores it. It does not establish who authored the file. It does not make a flawed process sound.

It proves that a particular TSA signed a timestamp token for a digest under its policy. That is useful — and it is a specific, bounded claim.

What does Label 309 not prove?

Label 309 does not become a qualified timestamp, and it does not replace jurisdiction-specific legal requirements. It does not identify a real-world person unless signatures and identity context are handled around the record. It does not prove truth, ownership, or compliance on its own.

What it proves is a public, independently verifiable commitment on Cardano — with optional layers for signatures, sealed content, recipients, and Merkle batching.

The short version

Use a Timestamp Authority when you need a recognized third-party timestamp — in PKI, document signing, or regulated legal workflows.

Use Label 309 when you need an open public proof that anyone can verify without the publisher or a single issuing authority.

Use both when the record matters enough that two independent timing layers are worth it.

For other angles on this comparison, Label 309 sits next to a Bitcoin-anchored approach in Proof of Existence vs OpenTimestamps and a software-signing approach in Proof of Existence vs Sigstore.