SMRFORGE

Sealed results gallery

Six signed bundles. Five shapes of result. One record.

Every card below is the same record, smrforge.result.v1 inside an Evidence Envelope, signed with the SMRFORGE production key. Download the raw JSON, verify it offline by recomputing the SHA-256 and checking the Ed25519 signature, then re-derive it by running the open engine on the inputs sealed inside it. The seal proves custody of the computation. It does not prove the physics is right.

1 · integrity, offline

$ smrforge verify <bundle.json>

Recomputes every SHA-256 in the manifest and checks the Ed25519 signature over the bundle hash. No physics is imported. The in-browser version does the same with no crypto library behind it.

2 · re-derive the number

$ smrforge reproduce <bundle.json>

Re-runs the open engine on the bundle’s own sealed inputs. Deterministic cards re-derive bit-identical. Monte Carlo cards carry a sealed tolerance, a re-run within 3σ.

3 · origin, decided by you

key ed25519:cfb88804…d69b52c

Origin is never a field in the bundle. Your verifier compares the signing key to the pinned production key in the trust root, and decides.

All six bundles below carry schema smrforge.evidence_envelope.v1, signature alg ed25519 over message bundle_sha256, public key cfb88804b92163566d485c8be3757baf74215944ad4852326457fcfd3d69b52c. Raw files are served from gitlab.com/smrforge/smrforge/packs.

Your number, sealed the same way

Bring a result a reviewer won’t take on faith.

A scalar, a field, a step, a comparison or a margin. We seal it as one of these records, you verify it offline and re-run it yourself. Engagements, pilots and Pro at support@smrforge.io.