CAIN-42 72-hour adversarial soak, started 2026-09-25 (UTC). IN PROGRESS until about 2026-09-28.

What runs: a dedicated 4-node CAIN-42 cluster (N=4, f=1, Q=3; fast path and DAG layer on) built
from git 1b28cf3. It gets continuous PBFT and DAG traffic, and a random node,
the primary included, is killed and restarted every 10 minutes. It is a dedicated cluster on
purpose: deliberately crashing the production cluster for 3 days is not a test.

Every hour a CHECKPOINT is published here. Each one contains:
  - every node's state (view, height, application-state hash);
  - the last 12 COMMIT and PREPARE quorum certificates from two nodes, taken straight from the
    running cluster;
  - a fresh consensus authorization enforced by MCPGate (ALLOW with a signed proof) and its
    replay (DENIED with a signed proof);
  - cumulative counters: requests, faults, restarts, view changes, divergences.
Each checkpoint carries the hash of the previous one, and is signed with the CAIN-42 evidence-root
key after the public-evidence privacy firewall clears it.

Verify at any time (Python 3.8+, pip install cryptography, no CAIN code):
  BASE=https://clawx.click/evidence/soak-72h-2026-09-25     # or https://cainstudio.online/proof/bundle/soak-72h-2026-09-25 (or mcpgate.online)
  curl -so verify_soak.py "$BASE/verify_soak.py.txt"
  curl -so verify_pbft_qc_bundle.py "$BASE/verify_pbft_qc_bundle.py.txt"
  python3 verify_soak.py "$BASE/"
  # prints each checkpoint VALID/INVALID; VERDICT: RUNNING (x of 72 h) now, PASS or FAIL when final.

A missing, reordered or edited checkpoint breaks the hash chain; an edited value breaks the signature.
Not claimed: independent failure domains (one host); that this is the production cluster.