LEIBODEX

Compute SHA-256 locally in your browser. Record a public hash timestamp and verify it later in Leibodex’s public append-only record.

ACTIONS

Save hashes across devices with My Ledger (no email).
Boundary

Leibodex records hashes and related technical artifacts. It does not verify identity, authorship, ownership, authenticity, legal validity, signer authority, admissibility, or chain of custody.

Bundle manifest (optional)
If you have the original bundle ZIP, inspect manifest.json locally (no upload).
No ZIP loaded.
—

WHAT LEIBODEX DOES

Leibodex computes SHA-256 locally in your browser. It can record the resulting hash in a public append-only system and later confirm whether a matching SHA-256 hash was recorded before the time shown.

No file upload happens in normal browser flows. Use Record for direct file hashes or Capture to build a provenance bundle locally before recording the bundle hash.

WHAT THE RECORD CAN SHOW

What a Leibodex record can indicate

  • A specific SHA-256 hash was recorded at the timestamp shown on its public verification page.
  • The same file or bundle can be rehashed later and checked against the same public SHA-256 hash timestamp record.
  • Published verification materials can be retrieved later for independent checking.

What Leibodex does not determine

  • Identity, authorship, legal ownership, authenticity, legal validity, signer authority, admissibility, or chain of custody.
  • Whether a linked file stayed online somewhere else after the timestamp was created.
  • Whether two similar files are equivalent if their SHA-256 hashes differ.

HOW IT WORKS

  1. Choose Record to hash a file locally, or Capture to assemble a provenance bundle in the browser.
  2. Leibodex receives the supplied SHA-256 value plus optional metadata, records it, and returns published verification materials.
  3. Anyone can revisit that record with Verify or a shared /verify/<hash> URL to check whether the same SHA-256 hash appears in Leibodex’s public record.

PRACTICAL USES

  • Record release artifacts, research PDFs, exported reports, scans, and bundle archives without moving raw files through a server in normal browser flows.
  • Create provenance bundles for image sets, receipts, and field documentation, then distribute the bundle alongside published verification materials.
  • Give operators and integrators public surfaces for record checking, exports, and independent audits.

Technical references live at Developers, Specifications, and Operational Principles.

Legal and policy details live at Terms, Privacy, Legal Notices, and Abuse Policy.

SUPPORT / TROUBLESHOOTING

If verify says Not found: recompute SHA-256 from the original file and retry with the exact hash.

If record or capture fails: retry once, then try a smaller file or a single file.

Need help? Report an issue.