PL ProofLedger Private timestamping

Browser-only SHA-256 proofing

Certify a file without uploading the file.

Drop a document, compute its fingerprint locally, then create a proof record you can verify later. This demo stores proof metadata in your browser and simulates the later blockchain anchor step.

File stays local Only the hash is recorded Verifiable by anyone
SHA-256 fingerprint Waiting for input

Fingerprint -> public anchor -> permanent proof

No blind trust, just reproducible math.

A production service would aggregate hashes into a Merkle tree, anchor that tree with OpenTimestamps or an RFC 3161 provider, then expose a portable evidence bundle. This MVP keeps the same product logic and UI, with the anchor represented as a transparent demo status.

Verification

Match the original content to a stored proof.

Verification recomputes the fingerprint in the browser. If the bytes differ by one bit, the result changes and the match fails.

Create or select a proof first.

Your local registry

Proof records

Trust model

How the platform works

  1. 01

    Prepare a stable document

    PDF is ideal, but any file works because the hash is computed over raw bytes.

  2. 02

    Compute the fingerprint locally

    The browser uses SHA-256 through Web Crypto. The original content never leaves the device.

  3. 03

    Anchor the fingerprint

    A real backend would batch hashes into a Merkle tree and anchor the root in a public timestamp system.

  4. 04

    Keep both halves

    The proof record and original file are useful together. Without the original, no one can recompute the match.

Basic

Private proof

Free

Local hash, metadata export, public proof page pattern, and self-verification.

Pro

Anchored certificate

$9 / proof

OpenTimestamps anchoring, downloadable evidence bundle, PDF certificate, and proof URL.

Identity

Verified owner

$29 / proof

Identity verification, RFC 3161 timestamp, audit trail, and business-grade exports.