AIR
Proof Lab
StartEcosystem
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself

Trust Card Live Generator

One page. Six fields. Hand it to anyone. Load any H33 bundle. Compute its hash in your browser. Render the card. Tamper one byte. Watch verification fail. Nothing mocked.

How this page works

This page loads /bundles/claim_84711.json by default. You can also paste any other H33 bundle. The page then:

(1) Computes a real SHA-256 hash of the bundle bytes in your browser using Web Crypto. (2) Parses the bundle to extract the six Trust Card fields. (3) Renders the card live. (4) Lets you tamper any byte and watch the card flip to FAIL.

This is a real verifier-shape demonstration. The page makes no network call beyond fetching the bundle file. H33 is not contacted during any of the computation.

STEP 1 / 4 · LOAD BUNDLE
Load an H33 evidence bundle
Default: claim_84711.json (the bond loss exposure demo bundle). You can also paste your own bundle JSON.
STEP 2 / 4 · COMPUTE HASH
Compute SHA-256 of the bundle bytes
Real Web Crypto in your browser. No upload. No external service. Production verifier uses SHA3-256; this demo uses SHA-256 because it's natively available in browser crypto. Same property: every changed byte produces a different hash.
STEP 3 / 4 · PARSE BUNDLE
Extract Trust Card fields from the bundle
Bundle ID · stated hash · three PQ signature envelope entries · corpus pin · timestamp.
STEP 4 / 4 · RENDER & VERIFY
Render the Trust Card and run the verifier
Six fields. One verdict. The verifier here checks that the bundle's STATED hash matches its COMPUTED hash, that all three envelope signatures are present, that the corpus pin parses, and that the anchor reference (if any) is well-formed.
The Trust Card
Verifier Output
Waiting for bundle…
Tamper Lab Break the bundle. Watch the card fail.

The whole point of a Trust Card is that tampering is detectable. The verifier compares the stated hash against the computed hash. Edit any byte of the bundle below and the computed hash will diverge from the stated hash. The verifier will return FAIL. The card will repaint with a red FAIL stamp.

This is what a regulator's local verifier does the moment a bundle arrives. No network call. No trust in H33. Just hash arithmetic.

or edit the bundle JSON directly below:
Take it with you
Download the bundle (JSON) Download the verifier binary See the full 8-step demo