The authentication argument gets all the attention. FRE 901(b)(9), process reliability, blockchain cryptography. But admissibility has two separate problems, and the hearsay question is the one that catches practitioners off-guard.
Picture this: opposing counsel stipulates to authentication. They're not challenging whether the process was reliable or whether the hash matches the file. Their objection is hearsay. The proof certificate, they argue, is an out-of-court statement offered to prove when the file existed. Authentication doesn't answer that.
FRE 803(6) does.
Authentication and Hearsay Are Not the Same Problem
FRE 901(b)(9) authenticates evidence from a reliable process or system. FRE 902(13), added in 2017, handles that through written certification. No live testimony required. Both answer the same question: is this what it claims to be?
Hearsay is a different question. An out-of-court statement offered for the truth of the matter asserted runs into FRE 802 unless an exception applies. The business records exception under FRE 803(6) is the relevant one here. For blockchain timestamps, building both arguments before a dispute starts is worth the work.
What FRE 803(6) Actually Requires
The exception covers records of regularly conducted activity. For a record to qualify:
- The record was made at or near the time of the event it describes
- By or from someone with knowledge of that event
- In the course of a regularly conducted business activity
- Making the record was a regular practice of that activity
- A records custodian can testify to those elements, or the record comes with certification under FRE 902(11) or 902(13)
- The opponent can't show the source or circumstances indicate untrustworthiness
The timing element is the one that trips people up. "At or near the time" means contemporaneous with the event. A blockchain anchor created weeks after an inspection, or after demand letters are exchanged, loses the 803(6) argument. The exception is built for routine records, not retroactive documentation.
Two Records, Two Separate Analyses
A blockchain evidence situation involves two distinct records. Conflating them creates gaps.
The first is the blockchain entry itself. A Polygon transaction or Bitcoin merkle proof is a machine-generated output of a cryptographic process. Courts analyze that under FRE 901(b)(9) as evidence from a reliable process or system. It's a computational output, not a human assertion about what happened.
The second is the proof certificate or receipt that documents the connection between a specific file hash and a specific on-chain transaction. That certificate is created at the time of anchoring, typically by an automated system, and delivered to the party as a record of what was anchored and when. Opposing counsel who frames that certificate as hearsay isn't wrong to try. Authentication alone doesn't close that objection. The blockchain ledger entry and the certificate are separate records, and each has its own admissibility path.
The Stronger Argument Runs Through the Party's Own Records
I think the cleanest 803(6) path isn't built on the service provider's documentation. It's built on the party's own.
If a claims team, forensic firm, or law department adopts a written protocol to anchor evidence files at intake, the anchoring record becomes part of that organization's business records. Created at intake. By the person who received the file. In the regular course of evidence handling. As part of documented standard procedure. That's the structure 803(6) was designed to cover.
The foundation then runs through the organization's records custodian, not the blockchain service. And if the certification path under FRE 902(11) is available, the custodian doesn't need to testify. A written certification covering the four 803(6) elements handles it.
This is the argument that holds up in practice. The service provider's documentation structure isn't what makes it work. The party's own workflow is.
Layering the Rules
Each rule answers a different objection.
FRE 902(13) provides self-authentication for machine-generated records through written certification. That's the answer to "is the blockchain record authentic?" without live testimony. FRE 803(6) covers the hearsay objection to the proof certificate, when the anchoring was part of regular business practice. Process reliability under FRE 901(b)(9) supports both.
Dual-chain anchoring adds to the 901(b)(9) argument specifically. ProofLedger anchors to both Polygon and Bitcoin. Two independent blockchains, separate consensus mechanisms, both recording the same file hash at the same moment. Process reliability through redundancy is harder to attack than a single-source timestamp.
No single rule does everything. The practitioners who think through all three before a dispute are the ones who aren't scrambling during the opening hour of a hearing to explain why they skipped a step.
What This Means Monday Morning
If your organization anchors evidence files as part of standard practice, document the practice explicitly. A written policy covering who anchors, when, using what process, and where the records are kept gives the 803(6) foundation something to stand on. Undocumented workflows and inconsistent practice create gaps opposing counsel will use.
Anchor at the earliest point in the workflow. First inspection, first receipt, first capture. The business records timing element requires contemporaneous records. Anchoring after a dispute is anticipated changes the analysis entirely.
For the authentication layer, prepare the FRE 902(13) certification before you need it. A written certification describing the anchoring process, the cryptographic method, and the chain of custody for the records is more useful built in advance than assembled under deadline.
The hearsay objection to blockchain evidence isn't common yet. But the argument is available, and opposing counsel is learning. Building the 803(6) foundation now, while it's a procedural choice rather than a gap to patch, is the right time to do it.
