Self-Authenticating Digital Evidence Under US Federal Rules

Self-Authenticating Digital Evidence Under US Federal Rules

A digital file can’t vouch for itself in a federal courtroom. Someone has to show it is what the party says it is, and for years that usually meant putting a witness on the stand. Since December 1, 2017, Federal Rules of Evidence 902(13) and 902(14) have offered a shortcut for some electronic evidence: a written certification from a qualified person can stand in for live testimony. Rule 902(13) addresses records generated by an electronic process or system, and Rule 902(14) addresses data copied from an electronic device, storage medium or file.

The shortcut has edges, though. It settles authenticity and nothing else, and it takes real paperwork. Below is how both rules work, what a certification has to do, where hash values come in, and how a blockchain timestamp record such as Certelo’s might support the process. That last part is analysis, not a guarantee.

First, what “authentic” means to a judge

Authenticating evidence means showing it is what its proponent claims. A screenshot has to be a real capture of the page it depicts. A log has to come from the system it supposedly came from. The general rule is Rule 901, which lists ways to make that showing, mostly by testimony of someone with knowledge.

Rule 902 is the exception list. Items on it need no outside proof of authenticity. Sealed government records and newspapers were on it long before electronic evidence. What the 2017 amendment added is a way to treat certified electronic evidence similarly, with a certification doing the work a witness would otherwise do.

Think of it as a change in who has to show up, not a change in what has to be proven.

Rule 902(13): records a system produced on its own

Rule 902(13) covers a record generated by an electronic process or system that produces an accurate result. The accuracy has to be shown by a certification of a qualified person that meets the certification requirements of Rule 902(11) or (12).

Think of machine output rather than something a person typed. Commentators point to operating system logs and registries, system-generated metadata, and automated geolocation data as typical examples. Commentary on the rule also stresses the line between records produced by an automated process and information entered manually by a person, which is why many practitioners treat 902(13) as a poor fit for, say, a typed spreadsheet.

The certification here speaks to the process. What does the system do, and why does it produce reliable results? It does not need to vouch for the contents.

Rule 902(14): copies, and why hashes matter

Rule 902(14) is the one that makes hash values famous. It covers data copied from an electronic device, storage medium or file, if authenticated by a process of digital identification, as shown by a qualified person’s certification.

The Advisory Committee’s note explains the logic. Copied data is “ordinarily authenticated by hash value.” If the hash values of the original and the copy differ, the copy is not identical. If they match, it is highly improbable that the two differ, so identical hashes attest that they are exact duplicates. The note adds that the rule is deliberately flexible enough to allow other reliable means of identification that future technology might offer.

Look at what 902(14) actually does. It lets a qualified person certify that they checked the hash of the item offered and that it matched the original. It is a statement about sameness between two copies. It says nothing about whether the original was truthful, who made it, or when. That distinction matters later when we get to timestamps.

The paperwork: certification and notice

Neither subsection is automatic. Each depends on a certification that complies with the requirements of Rule 902(11) or (12), and each requires the proponent to give the adverse party reasonable written notice before trial, with the record and certification made available for inspection. The point of the notice is to give the other side a fair chance to challenge.

For a domestic record, a certification is typically a signed declaration made under penalty of perjury. Practitioners commonly rely on 28 U.S.C. § 1746 for this, but that is something to confirm with counsel for your own matter.

A workable certification usually covers a few things. Who is the person and why are they qualified to speak about this system or process? What did they do, and how? What was the result? For 902(14), which hash algorithm was used, and what were the values for the original and for the copy? The details belong to the lawyer drafting it, and requirements can differ by court and by case.

Timing deserves a calendar entry. Because notice is required before trial, these certifications are not something to improvise a week out. The October 2026 Evidence Rules agenda book even records members discussing how late certifications arrive in practice in criminal matters.

What a certification cannot do

Here’s the paragraph that most summaries bury. The Advisory Committee note says plainly that a certification can establish only that the item meets the admissibility requirements for authenticity. The opponent can still object on other grounds, including hearsay, relevance and, in criminal cases, the confrontation right.

The committee’s own example is a defamation case. A plaintiff offers a printout of a webpage, with a certification describing how the page was retrieved. The page may be authentic, yet the defendant can still argue he never put that statement there. Likewise, certifying a spreadsheet shows the output came from the computer. It does not stop someone arguing the output is unreliable.

So “self-authenticating” does not mean “admitted,” and it certainly doesn’t mean “true.” It means one hurdle has been cleared on paper.

Where a blockchain timestamp fits (analysis)

Now to Certelo. Everything in this section is our analysis of how the pieces could relate, not a statement that any court has accepted a Certelo record, and not legal advice.

Certelo computes a SHA-256 hash of a file locally, so the original file doesn’t have to be uploaded to create the proof. That hash is then anchored to the Electra Protocol blockchain. The result is a publicly checkable record that this specific digital fingerprint existed at or before the recorded blockchain time.

That structure lines up with both subsections in different ways.

Under the logic of 902(14);

a qualified person could re-hash the document a party is offering and compare it to the hash recorded on-chain. A match supports the statement that the file offered is bit-for-bit the same as the file fingerprinted earlier. This is an adaptation of the committee’s copy-versus-original logic. The “original” is the file as it was when the hash was anchored. Whether a court sees it the same way is for counsel to argue.

Under 902(13);

the blockchain record itself is arguably a record produced by an electronic system. A certification would then need to describe how the system generates and stores that record and why its results are accurate. That is a harder showing than the hash comparison, and it likely needs someone who actually understands the protocol.

Neither route establishes authorship, ownership, originality or the identity of whoever created the file. The timestamp shows existence of a fingerprint at a time. If those other facts matter in the case, they need their own proof.

A walk-through (hypothetical)

Take an invented small design studio. In March, it timestamps its final product specification PDF with Certelo and keeps the certificate. Two years later there’s a contract dispute over what the spec said.

1- The studio’s counsel retrieves the stored PDF and generates a fresh SHA-256 hash.

2- That hash is compared with the hash on the blockchain record. Identical values support the claim that the PDF hasn’t changed since anchoring.

3- A qualified person writes down what they did, with the tool, the algorithm and both values.

4- Counsel gives written notice to the other side and makes the record available.

5- The opposing party stays free to argue the spec was never agreed, was superseded, or isn’t relevant.

The hash match gets the studio one thing: a stronger basis to say the document in hand is the one that existed in March. Whether the document means what the studio says it means is a different fight.

Deepfakes and rules still being written

The authentication rules are not standing still. The Advisory Committee on Evidence Rules has drafted a possible Rule 901(c) on fabricated AI-generated evidence. As of its October 15, 2026 agenda, the committee had prepared but not finally approved it. The draft would make the challenger show enough to support a finding of fabrication, after which the proponent would have to show authenticity by a preponderance of the evidence. The same agenda records that the committee withdrew the originally published version of proposed Rule 707 on AI-generated evidence and sent a modified proposal back for further study.

The practical reading is that nothing has changed yet. Even if a version were eventually approved, rulemaking timelines are long. During the May 2026 meeting, the committee chair noted that Rule 901(c) wouldn’t take effect before December 1, 2028 even if published that summer. Anyone relying on today’s rules should treat the draft text as a signal about direction, not as law.

For provenance work, there’s a useful takeaway in that debate. As synthetic media gets harder to spot by eye, evidence that a file existed in an exact form at an earlier time gets more interesting, because it doesn’t depend on judging how the content looks.

Let's deep dive

Does self-authenticating mean the evidence will be admitted?

No. It means the authenticity requirement is satisfied through certification. Hearsay, relevance and other objections remain available to the opponent.

Is a hash value alone enough under 902(14)?

The hash is the method, but the rule calls for a certification by a qualified person who actually performed the comparison. A printed number with nobody standing behind it doesn’t meet that.

Do I have to give notice to the other side?

Under both 902(13) and 902(14), yes. Written notice before trial, plus access to the record and the certification, is required.

Can a blockchain timestamp be self-authenticating?

It may be offered through a 902(13) or 902(14) certification, depending on what’s being authenticated. Whether a given court accepts it is decided case by case, and we aren’t offering a guarantee.

Does a Certelo timestamp prove who created my file?

No. It provides a verifiable record that a particular fingerprint existed at or before a point in time. It doesn’t identify the creator or establish ownership.

What if the file was modified after timestamping?

The hash would change, so the modified file wouldn’t match the on-chain value. That mismatch is how tampering shows up.

Does this apply outside the US?

No. This article covers the US Federal Rules of Evidence only. State courts and other countries have their own rules.