Don't trust us. Check us.

Verify a real bundle. Right here.

Below is a real SMRFORGE evidence bundle — a lab-grade OpenMC criticality result. Your browser is about to recompute every fingerprint and check the signature itself. No server. No SMRFORGE code. Then change a number and watch the seal catch you.

openmc-criticality.bundle.json

k_eff = ± —

— verdict: —

The two dashed boxes are editable. Change them to doctor the bundle — the check re-runs as you type. Everything else (fingerprints, signature) is sealed.

Provenance — what produced the number

data_library_sha256 ✎ editable

Sealed fingerprints (sha256sums)

Signature

alged25519

public_key—

bundle seal—

the check — running in your browser

and one step deeper — reproduce

Verify proves the file is untouched. Reproduce proves the number is real: a reviewer installs the open engine, re-runs it on this bundle's own recorded inputs, and the answer has to land inside the band the bundle sealed in advance. This part runs offline on the reviewer's machine — a browser can't run a Monte Carlo eigenvalue solve, and we are not going to pretend it did.

—3σ reproduce band — the re-run must land in here—

$ smrforge reproduce openmc-criticality.reproduce-demo.bundle.json

The bundle, the reviewer guide, and the open engine are public: how to reproduce it yourself.

How to trust this check. The key pinned in this checker is SMRFORGE's production signing key (fingerprint ed25519:cfb88804…d69b52c), generated in an offline ceremony. So a passing signature here proves both integrity (the bundle was not edited) and origin (that it was sealed by SMRFORGE). Don't take our word for the key: cross-check that fingerprint against our published trust root — the file at /.well-known/smrforge-trust-root and the DNS TXT record at smrforge-trust-root.smrforge.io. Origin holds only if they match.