H33 / Session / Public Verifier
One receipt verifies the meeting. Tamper it — REJECT.
Drag any H33 Session .h33pqv.json file below. We’ll check the canonical hash and verify all three post-quantum signature families (ML-DSA-87, SLH-DSA-256s, FALCON). PERMIT or REJECT in two seconds.
Or drop a .h33pqv.json file. Or paste it here:
Drag-and-drop runs entirely in your browser; verification runs on H33’s public demo verifier (Phase A backend at auth.h33.ai). The artifact contents are not stored.
What this means
Receipt narrative
Cryptographic verification details
Why "no login, no account"
If verifying a receipt required an account at H33, the receipt’s independence would be a lie. The verifier is public so the artifact can be checked by buyers, auditors, regulators, and adversaries on equal footing.
Why three signature families
The bundle is valid when at least two of three independent post-quantum hardness assumptions verify. Future obsolescence of one family doesn’t invalidate your receipt; compromise of two independently does.
Why drag-and-drop matters
This is the proof: any single byte changed after signing is caught by the canonical hash AND rejected by every signature family. Try the tampered sample to see it.