◆ Evidence workflows

Check the evidence file against the copy you collected.

At deposition, opposing counsel asks how you know the image or export is the one you collected. Record the acquisition hash at collection and retain the exact file. A later mismatch is strong indication of a change — and it says nothing about capture time, pre-submission edits, who handled the file, or a complete chain of custody.

The comparison point is in Base’s public transaction history rather than in our database, so an examiner can reach it without our API, our records, or our cooperation. It still needs the exact file and the receipt your process retained.

What happens if we shut down →
Public fingerprint
32 bytes recorded on Base
Exact file
Compare every character of the SHA-256 digest
Keep both
Retain the original file and receipt for later checks
Free check
Checking a file needs no account or credit

A finalized record means we observed a successful Base L2 receipt, not Ethereum settlement. Independent checking needs the retained file, receipt and suitable Base history access. Read the evidence limits.

◦ Use cases

Ways to use a dated file record

Vd

Ingest checkpoint

Record the digest produced by an evidence system at ingest and retain the exact file and processing record.

Cm

Export comparison

Compare a retained export with a recorded digest while preserving separate custody and access logs.

Sh

Independent inspection

Inspect the Base transaction without using the service database when the retained file, receipt, processing rule, and Base history are available.

▸ FAQ

Common questions, answered plainly.

Can this replace chain of custody documentation?

No. It records nothing about who handled the file. It is one external checkpoint inside your custody process — beside the documentation, never instead of it.

Does it satisfy FRE 902(14)?

No. That rule turns on a written certification signed by someone qualified to give it. The receipt data is material such a certification could describe; it is not the certification and it does not supply the certifier.

What does a mismatch actually tell me?

That the bytes or the processing rule differ from what was recorded. Anchor the acquisition hash at collection and a later mismatch is a strong indication of a change; it does not say when, how, or by whom.

Do I need an account?

No account is needed to check a file or download the independent verifier. Create an account and verify your email to notarize files and manage your records.

Need a dated record of this file?

Keep the source data and receipt. A matching digest supports a limited comparison; it does not establish truth, identity, authorship, ownership, custody, or a legal outcome.

Record this file →