This page explains how TimeBinder verifies when a file existed using cryptographic hashes and the Bitcoin blockchain, without storing or accessing the file itself.

Verification means confirming that a specific digital file existed by or before a particular point in time.

TimeBinder verification works by recomputing a file’s SHA-256 hash locally and comparing it to a cryptographic record anchored on the Bitcoin blockchain.

If the hashes match, the file is proven to have existed no later than the recorded blockchain time.

1. Verify a Proof of Time Certificate

Use your Proof of Time Certificate to confirm:

• The exact timestamp anchored on the Bitcoin blockchain.
  
• Bitcoin Blockchain transaction reference (TXID).
  
• The TimeBind bundle’s Merkle root hash representing up to 10 file hashes and optional reference and details data fields.
  
• A clear result: Verified or Verification Failed.

A “Verified” result proves the file existed at or before the blockchain timestamp. It does not assert authorship or truth of contents.

What time is actually being proven?

TimeBinder records multiple time points, including:

(1) the time a file hash is submitted to TimeBinder,
(2) the time that hash is submitted to the Bitcoin network as a transaction, and
(3) the time the transaction is mined into a Bitcoin block.
(4) the time the Bitcoin transaction is confirmed by at least 6 globally distributed servers.

The block mining time provides cryptographically verifiable proof that the file hash existed no later than that moment in time.

2. Verify by File Hash (No Upload Required)

Paste or drop your file. Your browser computes a SHA-256 hash locally; the file never leaves your device.

• Verification requires a live blockchain view to confirm on-chain data. Only the hash is processed client-side.
  
• Hash verification does not search unknown records. It confirms against TimeBinds linked to your account, a presented Proof of Time Certificate/QR, or items marked for public verification.

This process allows verification without revealing or transmitting the original file.

3. What You’ll See on a Match

• Timestamp and confirmation depth
  
• Original anchor transaction (TXID)
  
• Shareable verifier link suitable for court bundles

Your file stays private; verification uses only the hash.

These details are sufficient for independent verification by third parties.

4. ASAP vs Pooled Verification

5. Verification Results Explained

TimeBinder compares your file hash to the TimeBind bundle metadata and the blockchain record. Results are:

✅ Verified	The file hash and its inclusion proof match the Merkle root anchored on the Bitcoin blockchain. ASAP: Root appears in OP_RETURN on the public Bitcoin blockchain; confirm via the TXID shown on the Proof of Time Certificate. Pooled:Verified by Merkle inclusion prooflinking your leaf to the pooled root. Use the verifier or any independent Merkle tool with the provided proof data.
❌ Verification Failed	No match to a recorded TimeBind. Typical reasons: • The file was modified after TimeBinding so the hash no longer matches the TimeBound hash. Question if the file has been tampered with. A failed result does not imply malicious intent. It indicates the presented file does not match a previously TimeBound hash.

Proof of Time Certificate and QR

The Proof of Time Certificate and its QR code link identify the relevant Bitcoin transaction and Merkle root. For pooled proofs, the inclusion path is provided dynamically by TimeBinder when verifying; it is not embedded in the certificate itself.

The certificate provides all information required to reproduce verification independently.

6. What Verification Does Not Do

Verification confirms when a file existed.

It does not prove who created the file, whether its contents are accurate, or whether it is legally admissible on its own.

Verification is designed to support authenticity assessments, not replace legal or factual analysis.