Generate proof locally
The browser computes SHA hashes and drafts a manifest without uploading the original file bytes to the service.
Linked Projects • Open Provenance
AttestLog is open provenance infrastructure for digital integrity, chronology, signatures, chain of custody, public auditability, and long-term trust continuity.
What exists now
The current prototype lets a user select a file locally, compute content hashes, generate a portable manifest draft, register that manifest, and later verify a file against the recorded proof.
The browser computes SHA hashes and drafts a manifest without uploading the original file bytes to the service.
Submitted manifests receive log metadata, a Merkle root, an inclusion proof, and a public proof URL when registered.
Later verification recomputes file hashes, compares the manifest, and checks whether the manifest is included in the registry.
Architecture
AttestLog treats the manifest as the portable protocol object, not the file. Storage can live elsewhere, visibility can be public or private, and the proof can remain independently verifiable.
Trust continuity
Digital provenance will only matter if records can move across storage providers, signing schemes, registry operators, and future verification tools without losing their meaning.
The manifest remains the durable object users can download, copy, inspect, register, and verify outside a single website session.
Append-only registry records preserve chronology and make later tampering visible through inclusion and consistency proof design.
The first public site already supports local proofs, registry submission, proof URLs, and later file-to-manifest verification.
Use it now
Open the product site to generate a local proof package, register a portable manifest, or verify a file against a saved manifest and registry record.