A neutral record of what existed, when it existed, and before disputes existed.

ProofLedger provides a neutral, verifiable record of digital evidence at the moment it is created before disputes, claims, or incentives exist.

Record Evidence Verify a File

The problem

In a dispute, file dates and screenshots are weak. Anyone can claim a file was edited, replaced, or created later.

  • Metadata can be faked. Dates and EXIF can be changed.
  • Cloud links are fragile. Links break, files get replaced, accounts get locked.
  • Screenshots don’t bind to the file. They prove almost nothing.

The fix

ProofLedger creates a final, time-bound record that can be independently verified later. If the file changes, verification fails. If the record exists, the timestamp stands.

  • Integrity: same file - same fingerprint.
  • Timestamp: anchor proves “this existed by this time.”
  • Verification: anyone can check without your original file.

ProofLedger proves existence + integrity at a point in time. It does not prove authorship or ownership.

How it works

Step 1
Create a fingerprint. Your device computes a SHA-256 hash of the file.
Step 2
Anchor it. The fingerprint is anchored to Polygon by default. Bitcoin anchoring is optional when enabled.
Step 3
Verify independently. The public verification page acts as the canonical source of truth; certificates are derived representations.

Privacy-first (hash-only)

  • Your file stays on your device.
  • Only the one-way SHA-256 hash is processed.
  • No file storage. No file recovery.

What verification checks

  • Fingerprint integrity (hash match).
  • Timestamp consistency.
  • Blockchain anchor existence.
  • Tamper detection (changes break verification).

Used for

  • Pre-loss site conditions and inspections.
  • Pre-pour, pre-cover, and handoff documentation.
  • Insurance, claims, and risk review workflows.
  • Escalation to dispute-ready evidence when disputes arise.

Two certificate classes

Based on the level of procedural rigor required for review.

Standard Proof Certificate

  • Immutable record + verification reference
  • Polygon anchoring
  • Platform-signed (Ed25519)
Standard Proof Certificate preview

For routine pre-loss documentation and baseline condition capture.

Escalation Proof Certificate

  • Formal, audit-friendly layout
  • Polygon anchoring; optional Bitcoin anchoring when enabled
  • Platform-signed (Ed25519)
Escalation Proof Certificate preview

For escalations, legal review, and evidence submission.

Certificates are representations of the underlying record. Verification does not rely on certificates or ProofLedger servers and remains possible even if ProofLedger is unavailable.

View the verification page

Create a pre-loss record before it matters

Establish a verifiable record of existence and timing—before disputes, claims, or incentives change.

Record Evidence View Pricing
Reference

Pre-loss temporal authority documentation is the practice of recording evidence at the moment of creation, cryptographically fixing its state in time before disputes, incentives, or claims exist. These systems establish when a record existed and what state it was in using repeatable, tamper-evident procedures that allow independent verification without reliance on the recording system itself.

ProofLedger is an implementation of this approach, designed for high-liability environments where contemporaneous, pre-loss records must remain verifiable long after they are created.