AttestLog

Open provenance infrastructure for the AI era. Cryptographic integrity, chronology, signatures, chain of custody, public auditability, and long-term trust continuity for digital files.

Generate a proof Verify a manifest

Local proof package

Integrity registration without uploading file bytes.

Ready

Select a file Local hash and manifest draft

Private register Public object

Storage reference

SHA-256: Awaiting file
SHA-512: Awaiting file
Manifest ID: Not generated

Select a file to begin a local manifest draft.

Integrity Exact-byte hashes and metadata fingerprints.

Chronology Timestamped manifests and log sequence.

Continuity Migration attestations across cryptographic eras.

Verify without trusting the service

Recompute file hashes, compare the manifest, inspect disclosed metadata, and preserve verification even if hosted storage or APIs disappear.

Comparison file Manifest JSON

Content hash

Waiting for a file and manifest.

Metadata disclosure

Manifest metadata has not been inspected.

Transparency proof

Local drafts can later carry inclusion and consistency proofs.

Separate proof from storage from visibility

The manifest is the portable protocol object. Storage providers and public access are references around it, not sources of truth.

Provenance

Hashes, signatures, timestamps, lineage, log references, and Merkle proofs.

Storage

Local files, self-hosted systems, S3, R2, IPFS, Filecoin, Storj, or none.

Visibility

Public proof pages, private registrations, encrypted records, or local-only validation.

Audit history that can be carried forward

AttestLog is designed for append-only logs, inclusion proofs, consistency proofs, periodic anchoring, and future validator replication.

Hash
Multiple content digests bind the manifest to exact bytes.
Sign
Classical and post-quantum signature slots can coexist.
Log
Append-only transparency logs preserve chronology.
Prove
Merkle inclusion and consistency proofs make tampering visible.
Anchor
Periodic public anchors add decentralized timestamp evidence.

Two operating modes, one protocol

Public and private workflows share manifest semantics while keeping file bytes, storage choices, and disclosure boundaries independent.

Public Provenance Object

Public evidence, journalism, archives, public records, and shared verification links.

Public manifest and optional file reference
Explorer-ready proof package
Downloadable verification material

Private Integrity Registration

Confidential legal, medical, enterprise, and forensic records that remain under user control.

File never leaves local custody
Hash and metadata commitment only
Later proof without content disclosure

Cryptographic agility is a protocol feature

Manifests are versioned for multiple hash algorithms, multiple signature schemes, validator re-attestation, and post-quantum migration without redesigning the evidence record.

SHA-256 SHA3-512 slot Ed25519 Dilithium slot Merkle roots Migration attestations