Verify a Receipt Credential.

Drop a .h33pqv.json credential file. The verifier checks its integrity hash against the embedded signature, walks the evidence trail (participants, grants, executions, findings), and renders a single verdict. Offline. No H33 access required.

What VALID means here. This public verifier renders an integrity verdict: the credential’s content-hash matches its embedded mock_sig signature, so nothing has been altered since it was issued. It is a harness — production credentials carry the real 3-of-3 post-quantum signature (ML-DSA + FALCON/FN-DSA + SLH-DSA, all three must validate). VALID means the receipt reproduces unmodified; it does not mean the session was secure, correct, or compliant. For the production offline verifier see the Portability Verifier and the owned capability at Verification.

◆

Drop Receipt Credential here

drag a .h33pqv.json file · or click to select

no file handy? Open the meeting product, issue a grant, click Download .h33pqv.json in the Receipt modal, then drop it here.

Where this sits: independent Verification

This page is a consumer of Verification — it independently renders the verdict on a PQ-Video receipt credential it did not produce, reproducing the credential and confirming its signature. It consumes an artifact; it does not produce the evidence (that is H33-74), does not monitor the session over time (that is HATS), does not score maturity (that is HICS), and does not govern the decision (that is Agent-008).

FAQ

What does a passing verdict mean — and what does it NOT mean?
VALID means the credential reproduces unmodified and its content-hash matches its embedded signature. It does not mean the meeting was secure, the decision correct or fair, or anything compliant — that boundary is what makes an independent verdict meaningful.

Is the verifier independent of H33?
Yes. It runs entirely in your browser against a local file; there is no network call to H33. The credential travels with its own verification instructions and public-key bundle reference, so it verifies with H33 absent.

How is Verification different from HATS, HICS, and Agent-008?
Verification renders an independent verdict on an artifact that already exists. HATS records and monitors operational evidence over time; HICS scores maturity; Agent-008 governs the decision. This page only reproduces and validates.

Is this the real post-quantum signature check?
No — this public page is a harness. The signature here uses a deterministic content-hash with a visible mock_sig prefix; production credentials carry the real 3-of-3 PQ signature (ML-DSA-65 + FALCON-512 / FN-DSA + SLH-DSA-SHA2-128f, all three must validate; FN-DSA / FIPS 206 is still a draft). Use the Portability Verifier for the production offline verdict.

Is the VALID result hardcoded?
No. The verdict is recomputed from the credential bytes every render: the content-hash is derived with the signature field excluded and compared to the embedded value. Use Hostile Mode above — any tamper flips the verdict to INVALID immediately.