Offline Verifier — Verify cryptographic evidence without servers, accounts, or network

Schedule DemoLaunch H33
Pricing
Log InGet API Key
Sample receipts · in your browser
Offline Verifier
One verifier. Every H33 artifact.
Verify cryptographic evidence with no server, no account, and no network. One engine — growing to cover every H33 proof.
Supported today
Replay Bundle v1
Coming
H33-Key Materialization Receipt
H33-74 Receipt
HATS Evidence
APQC Conversion Receipt
Agent-008 Governance Receipt
As each verifier becomes real, the circle becomes a checkmark. The page verifies only what's actually supported — honest by design.
Exhibit 07
A sample replay bundle (public demo key, no issuer verification).Replay Bundle v1 · sample
Every governed operation seals its state into a portable receipt — an H33-74 commitment signed with post-quantum ML-DSA-65. It carries its own public key.

Receipt body

Cryptographic seal

✓ ML-DSA-65✓ FIPS 204✓ H33-74✓ Portable
H33-74 commitment · SHAKE256 · 74 bytes
ML-DSA-65 signature ·
Exhibit 11
Offline.
The verifier runs entirely in your browser as WebAssembly — the same engine used for genuine receipts. No server is contacted.
    Real ML-DSA-65 (FIPS 204) + H33-74 (SHAKE256), compiled to WebAssembly.
    Public demo key · no issuer verification. A VALID result shows the receipt is internally consistent with the public key it carries. It carries no authenticity: it does not show that H33 issued the receipt.
    Exhibit 12
    What happens if H33 disappears?
    The verifier is local and the receipt is portable.
    Internet disconnected✓ Verification succeeds
    DNS unavailable✓ Verification succeeds
    H33 servers offline✓ Verification succeeds
    Demo illustration, not a live test: the verifier makes zero network, DNS, or time-of-day calls — so none of these can change the result.
    loading verifier… Sample is labeled sample; verification is performed by the same engine used for genuine artifacts. Real ML-DSA-65 + H33-74.

    Verify your own receipt.

    Paste any H33 receipt bundle, or drop a .json / .h33 file. Verification runs in your browser (public demo key; no issuer verification).

    Awaiting a receipt…
      Awaiting receiptno network · verified in your browser
      Public demo key · no issuer verification. A VALID result shows the receipt is internally consistent with the public key it carries. It carries no authenticity: it does not show that H33 issued the receipt.

      Why trust this?

      What this proves — and how to check it

      This page reinforces one claim Verification makes: an H33 artifact is designed to be independently verified (not yet available for production receipts).

      Reproduction path — no server, no account, no network:
      1. Inputs → paste your own H33 receipt / replay bundle above (or the labeled sample).
      2. Verifier → real ML-DSA-65 (FIPS 204) signature check + H33-74 (SHAKE256) commitment recomputation, in-browser WASM.
      3. Verdict → VALID / INVALID. Change one field and it flips to INVALID.

      The hero artifact is a labeled sample replay bundle — not live production evidence; the "verify your own receipt" panel is a live check of whatever you supply. The sample is signed with a public demo key, and the verifier checks the ML-DSA-65 signature against the public key the bundle carries, with no issuer verification. Receipts here therefore carry no authenticity: a VALID result shows internal consistency with that key, not issuance by H33. See independent verification · HATS proof lab · Verifier CLI.

      One verifier. Every H33 artifact. Offline.

      Supported today: Replay Bundle v1. More coming.