Status: Public Beta v0.2 · ProofSpec v0.1 · API v0.2 · Privacy-first · No blockchain

Create / Verify

Hash locally. Request a signed timestamp from the stateless API. Download your proof file .tproof.json, then verify it later. Your content never leaves your device.

v0.2 is proof-file first: verification requires the .tproof.json file.

Create a proof Verify a proof

Developers: integration examples live in API Docs. The protocol is defined in ProofSpec.

Step 1 · Create

Create a proof file

Choose text, a file, or an existing SHA-256. Hashing runs locally in your browser.

Input mode

Text to hash

Type (optional)

Meta (optional, non-sensitive JSON)

Do not include personal data. Meta is optional and should remain non-sensitive.

Status—

Hash (fingerprint)—

Issued at (server)—

Signature—

{}

Keep the .tproof.json proof file. Verification requires it.

What this proves: an exact content fingerprint (SHA-256) existed at the server-issued time and is signed by the TimeProofs key.
What this does not prove: authorship, intent, delivery, or that someone read/accepted anything.

Step 2 · Verify

Verify a proof file

Select your .tproof.json proof file, then verify its signature.

Why a proof file is required: the .tproof.json contains the timestamp + issuer + signature. A hash alone cannot prove when it was issued or by whom it was signed.
If the file is corrupted, unsupported, or invalid, verification is rejected.

Proof file (.tproof.json)

…or drag & drop a .tproof.json file here

Status—

Hash (proof)—

Issued at (server)—

Signature—

Overall validity

—

Signature (Ed25519)

—

{}

What is verified: the proof file’s structure and cryptographic signature (issuer, timestamp, and the referenced SHA-256).
What is not verified: this does NOT verify your original file automatically — it verifies the proof. To check a file, you must re-hash the exact file and compare it to the hash inside the proof.

Need integration snippets? Use API Docs.
Need the formal spec? Read ProofSpec.