empirical
Four hosts. Two GPU families. Two CUDA toolchains. Two PyTorch wheels. 90 samples each. The same rollout re-executed everywhere lands on one bit-identical digest — so the validator can re-run a miner's decode and reject any nondeterminism.
count
hosts
count
samples / host
result
digest agreement
bit-identical across classes
canonical sha2564de1918431de…e960572c· 32 segments compared · 0 divergent
every row ran the same 90-sample workload · a single-byte drift would surface as a red segment in FIG.01 · none observed
why it matters
If two honest miners on different GPUs produced different proofs for the same completion, mesh consensus would fail — not because anyone cheated, but because of numerical drift. Reliquary's proof envelope is sized to absorb long-sequence attention drift, while remaining tight enough that tampering is caught. The matrix above shows the envelope has substantial headroom: the honest path across four distinct hardware + toolchain combinations produces byte-identical digests, so the validator can re-execute any miner's decode and gate nondeterminism the instant a digest diverges.
Full reproduction steps + per-sample digests are committed in reliquary-ledger/docs/audit/cross_gpu.