Fingerprint & verify any document — free, no upload Try it now →

// premium service · the verified evidence package

The Verified Evidence Package

For when a proof has to perform.

Checking a LedgerProof receipt is always free. The Verified Evidence Package is the premium layer for the moment a single proof has to stand up in front of someone who matters — and be read, re-verified, and weighed by a third party who trusts neither of you. It's a paid service: this page explains it, but there's nothing to install or run here.

§Litigation exhibit §Regulator's evidence request §Audit workpaper §Insurance claim

how it works

It re-proves the whole chain — then fails closed.

Give the engine a content hash and a proof reference. It re-verifies the full integrity chain against the live public chain. If anything is off, it refuses to issue a bundle.

01

Content hash

The SHA-256 of your record — the document itself never leaves your hands.

02

Entry

Resolves the hash to its signed entry in your account's hash chain.

03

Merkle root

Recomputes the Merkle root from the entry and its inclusion proof.

04

Public ledger

Matches that root to the anchor on the public chain via a public-ledger transaction.

Any mismatch → the engine returns HTTP 422 and issues nothing. A Verified Evidence bundle only exists when the entire chain verifies.

what's in the bundle

Everything a third party needs to weigh it — without trusting us.

Verification result

The pass/fail outcome of the full content-hash → entry → root → public-chain check.

Attestation

A plain-English statement of existence and integrity — with its assertion limits stated up front.

Anchor evidence

The public-chain txid, block, Merkle inclusion proof, and the raw OP_RETURN bytes.

📋

Chain of custody

A contemporaneous record of the verification and how the bundle was produced.

Offline re-verification

Step-by-step instructions to re-check the proof against the open verifier, with no dependency on LedgerProof.

🛡

Privacy posture

An explicit record that no document content was transmitted or stored — only hashes.

Hash-only. Your document never leaves your hands.

The engine receives a SHA-256 content hash and a proof reference — never the document. Nothing containing your content is transmitted to or stored by the service: document_persisted_server_side: false. The strongest privacy posture is the Enterprise path, where hashing happens in your own stack via the SDK, so the content never even reaches the wire.

premium · two ways to buy

Package one proof, or build it into your pipeline.

A premium capability — access comes with a paid plan or per bundle. The open verifier stays free and separate; it's checking that's free, packaging that's paid.

Standard

Verified Evidence

Usage-based · per bundle
  • A verified, dispute/audit-grade bundle from any anchored receipt
  • Plain-English attestation with the assertion limits stated
  • Full public-chain anchor evidence + Merkle inclusion proof
  • Contemporaneous chain-of-custody record
  • Standalone offline re-verification
Talk to us

Enterprise

Verified Evidence at scale

Custom · annual + volume
  • Everything in Standard
  • Counsel-gated § 1746 expert-declaration template, for a qualified signer
  • In-pipeline generation via SDK / API, with per-account metering
  • Higher volume, priority support, and a signed DPA
  • Dedicated onboarding for legal, compliance, and claims workflows
Talk to us

It is also built into the Vault — the Business and Enterprise plans include the Verified Evidence Package, so your system of record and your court-ready exhibit come from one place.

See Vault pricing

What it proves — and what it doesn't

A LedgerProof proof is tamper-evident, not tamper-proof: it shows whether a record changed, and the assurance deepens with public-ledger confirmations. The Verified Evidence Package proves a record existed and is intact at a point in time — not that its contents are true, accurate, complete, or who authored them. The bundle is built for the admissibility analysis your counsel performs under FRE 902(13)/(14) — jurisdiction-specific, and never a guarantee of admissibility. Free verification with the open verifier always stays free. This is not legal advice.