The threshold

KEY RECOVERED only when the chip hits the key at least 2.0× as often as /dev/urandom over the same 4,096 shots. The comparison is raw: qpu_hits ≥ 2 × urandom_hits. The margin shown (like 3.1×) is rounded half-up to one decimal for display only.

Set on day 0: 2026-10-10T15:00:00Z
sha256 of the threshold block: 1c88746999481a27534f0c5cc25504c3338c64cb6f4456f1148910ecc4a25e26

{
 "VERDICT_MARGIN_MIN": 2,
 "SHOTS": 4096,
 "rule": "RECOVERED iff qpu_hits >= VERDICT_MARGIN_MIN * urandom_hits over the same SHOTS",
 "threshold_set_at": "2026-10-10T15:00:00Z"
}

Why it is never tuned

A threshold you can move after seeing results is a result you can fake. The services refuse to start if this block's hash changes after the first completed attempt.