◆ Journalism records
Date the source material before you publish.
The story runs and the subject says the document was altered or the footage was cut to mislead. Record the file at ingest, before any edit, and again at the version you publish from. It speaks to the bytes — never to who supplied them, to what they depict, or to a complete edit history.
The record is a Base transaction outside our database, so a subject disputing the story can check it without asking us for anything. Keep the ingest file and the receipt; those are what the check runs against.
What happens if we shut down →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
Source-file version
Keep original files and receipts beside source, device, location, and consent records.
Edit boundary
Checkpoint a selected pre-edit or publication version and document the processing steps separately.
Disclosure packet
Combine the Base checkpoint with independently validated provenance credentials when the newsroom uses them.
▸ FAQ
Common questions, answered plainly.
The subject says the document was altered.
Record the file at ingest, before any edit, and again at the version you publish from. A later copy either reproduces the recorded fingerprint or it does not.
Does it say anything about who gave me the file?
No. It speaks to the bytes and nothing else — never to who supplied them, and never to whether what they depict is true.
Does the source’s file become public?
The file body never leaves your computer; what goes on chain is a 32-byte fingerprint. It is not encryption, though: if a document’s contents are predictable, someone can test a guess against the fingerprint.
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.