✓
TSI IP Vault — Independent Verifier

Don't trust us. Check it yourself.

This page recomputes the entire TSI IP Vault hash chain in your own browser. No account, no API key, no server-side step you have to take on faith.

Why this exists: a proof you can only check by asking the person who made it isn't a proof — it's a promise. Everything below runs as JavaScript on your machine using the browser's own SHA-256. Save this page (Ctrl/Cmd-S) and it still works with the network unplugged, years from now, even if this company is gone.

1 · Load the ledger

Fetch it live, or paste a copy you saved earlier — an old copy is the stronger test, because we can't change what you already hold.

2 · Verify the chain

Recomputes every entry's hash from its own fields and confirms each one commits to the one before it. Any edit, insertion, deletion or re-ordering breaks the links from that point on.

Amendment history

A sealed record is never edited. If something needs correcting, the correction is sealed as its own new, chained entry that points back to the original via addendum_to — so the whole trail stays visible and tamper-evident. Nothing is ever quietly changed.

3 · Verify a document

Have a copy of a sealed document? Drop the file, or paste its exact text. We hash it here and look for that fingerprint in the chain. Your file never leaves this page.

Drop a file here — or click to choose

4 · Verify a proof certificate

A proof certificate is a small, self-contained file: one proof, the short stretch of chain from that proof to an anchored root, and where that root was anchored. You don't need the full ledger for this. Paste it, open a saved .json, or fetch it by proof ID.

Verify it by hand (no code, no us)

  1. Canonicalize {seq, proof_id, public_title, content_sha256, sealed_at, prev_hash} per RFC 8785 — in practice: sort keys, minify JSON.
  2. SHA-256 that string → it must equal that entry's entry_hash.
  3. Each entry's prev_hash must equal the previous entry's entry_hash; entry 1 uses the literal GENESIS.
  4. The final entry's entry_hash is the published root.
  5. For a proof certificate: run steps 1–3 over its chain_segment; the last entry's hash must equal anchor_root, and the anchored text is TSI-CPV1: followed by that root.

Any SHA-256 tool on earth reproduces this. Nothing here is proprietary — that's the point.