Independent Verification

Download the bundle. Run the verifier. Get the same result. No H33 contact required.

Most evidence systems require trust in the vendor that produced the evidence. H33 evidence requires no such trust. Every bundle is independently verifiable: download the bundle, run the open-source verifier, and get the same result as anyone else running the same verification. Regulators, auditors, customers, and acquirers verify on their own infrastructure, without contacting H33, without phoning home, without trusting H33's servers to be alive.

The independent verification standard

A verification is independent when it satisfies four properties: The verifier does not contact the vendor. No API call to H33. No license check. No phone-home telemetry. The verifier does not require vendor cooperation. The vendor does not need to confirm the bundle is real, valid, or hers. The verifier is reproducible. Two parties running the same verifier on the same bundle reach identical conclusions. The verifier is open. The verification protocol is published. The implementation is open source. H33 verification satisfies all four.

What gets verified

The verifier checks every property the bundle asserts. Structural integrity. The bundle parses as canonical JSON. The schema version is recognized. Required fields are present. Cryptographic integrity. The three independent post-quantum signatures verify against the bundle's commitment. ML-DSA-65, FALCON-512, and SLH-DSA-128f are each checked. Evidence control integrity. Each of the eight evidence control objects validates against its specification. Anchor integrity (if present). If the bundle's anchor field is populated, the verifier optionally queries the chain to confirm inclusion. Sidecar integrity. Each sidecar's digest matches the bundle's reference. Each check produces a pass-or-fail verdict.

The verification command

curl -O https://h33.ai/bundles/claim_84711.json
curl -O https://h33.ai/downloads/h33-verify
chmod +x h33-verify
./h33-verify claim_84711.json

Output: bundle id, profile, substrate, per-EC verdicts (all PASS), Anchor PASS, Overall PASS. "H33 was not contacted during this verification." Exit code: 0.

Who verifies and why

Regulators. A regulator reviewing a regulated entity's evidence runs the verifier offline. The verification result is binding because the verifier is reproducible. Auditors. An external auditor reviewing a client's evidence runs the verifier. The audit verification is independent of the client's controls and the vendor's representations. Insurance carriers. A carrier evaluating an insured's claim evidence runs the verifier. Reinsurers. A reinsurer reviewing a primary carrier's evidence runs the verifier. Acquirers. An M&A due diligence team running verification independent of the target's representations. Customers. An enterprise customer reviewing a vendor's evidence runs the verifier. Courts. Litigation discovery surfaces evidence. Both sides run the verifier. Both sides agree on what the verifier returns.

What independence requires

True independence requires that the verifier be open source (so the verification logic is auditable), deterministic (so two runs produce the same output), self-contained (so it does not call out to the vendor), reproducible (so any party can build it from source), and standards-aligned (so alternative implementations are possible). H33 satisfies each. If H33 ceases to exist tomorrow, the verifier continues to work.

Common questions

Can I implement my own verifier?
Yes. The verification protocol is published. The reference implementation is open source.

Does the verifier work offline?
Yes. The base verification is fully offline. The anchor verification requires querying a public blockchain RPC, which is independent of H33.

Is there a UI version?
The reference verifier is a CLI tool. UI implementations are straightforward to build.

What's the verification performance?
A typical bundle verifies in tens of milliseconds. Batch verification of millions of bundles is bounded by I/O.

Can I script the verifier into my CI/CD?
Yes. The verifier returns standard exit codes (0 for pass, non-zero for fail).

Get Started

Run the demo Download the verifier Download a bundle