Orphograph

Need provenance for your own dataset? The data never leaves your machine — only fingerprints are anchored.

How dataset provenance works →

Dataset Provenance Certificate

Orphograph seal

anchored to Bitcoin via
OpenTimestamps

—files
—total size
Receipt ID
Merkle root (SHA-256)
Algorithm
Status
Calendars
BTC pinned at

What this certifies

  • This dataset, its license/consent documents, and its acquisition log all existed in this exact form by the anchored date.
  • No file has been added, removed, or modified since — any change alters the Merkle root.
  • Each file is independently verifiable below, without re-disclosing the rest of the set.

What it does not certify

  • That the data was lawfully sourced, licensed, or owned.
  • That the acquisition log is truthful or complete.
  • Authorship of any file.

Corroborating evidence of integrity and time — not a license, not ownership.

File manifest

#FileSHA-256Size

Verify a file is in this set

Both checks run entirely in your browser — the file never leaves your device. Drop a file to check it by its contents, or verify a known path against its Merkle inclusion proof.

Drop a file here, or click to choose.

We SHA-256 it locally and check the fingerprint against this dataset's manifest.

…or verify by path (with full Merkle proof)

Enter a path (or click a row above). We fetch its inclusion proof and recompute the root in your browser; if it equals the certified root, that file is provably part of this dataset.

OpenTimestamps proofs — the root, anchored to Bitcoin

    Independent verification — don't trust us, check the chain

    The Merkle root above is what lands on Bitcoin. The links below go to public, third-party services we don't run. If any one shows the root anchored, the proof holds — even if orphograph.com disappears.

    This certificate proves the Merkle root above was submitted to the listed OpenTimestamps calendars at the time shown, and that every listed file hashes into that root. The calendars aggregate the root into a Bitcoin transaction; each .ots file is independently verifiable against the public chain.

    To verify without trusting us: download the receipt JSON + the .ots files from /api/receipt/<id> and the manifest from /api/verify_folder/<id>, then run the open-source verifier at orphograph.com/verify/.

    Proof-of-existence only. Not a qualified eIDAS timestamp. Not a license or a determination of ownership. See Terms.