The same 64 bits, in your browser.

A 2.3 KB WebAssembly module — zero imports, compiled from the same det_math.rs the node ships — reruns VERSE's entire floating-point library in your browser's engine and folds every output bit into one digest. Published from native x86 and wasmtime: 0xb87421e672bdf23a. If your machine prints the same number, three unrelated compilers just agreed to the last bit — and that is the whole reason an honest re-run can catch a liar.

Run it herenothing is sent anywhere · it runs on this page

published0xb87421e672bdf23anative x86 · wasmtime · pinned in CI this browser—not run here yet

⏳ not yet run here

Reproduce it off the web toosame digest, from a clone

The browser is one engine. Clone the repo and reproduce the identical value natively (your x86/ARM), under wasmtime (cranelift), and under a JS engine (V8 / JavaScriptCore) — three independent wasm compilers:

cd verse-node
bash scripts/prove-det-wasm.sh   # native ↔ wasmtime  → 0xb87421e672bdf23a
bash scripts/prove-det-js.sh     # ↔ V8 / JavaScriptCore → same digest

This proves the floating-point math is bit-identical across engines — not that the network is trustless, and not that a whole capsule replays everywhere: the re-executing referee is still pinned to one wasmtime build, and a foreign engine abstains rather than convicts. Just the math — which is the part everything else stands on. (README's "portable vs pinned" line, in one page you can click.)