CAIN-42 Lab: verify the cluster yourself

Read first. PRE-PRODUCTION, same-operator sandbox on one host. What you can verify here: signatures, quorum-certificate votes and cross-node agreement. What you cannot verify here: independent failure domains, network partitions, a malicious validator, or that anyone outside the operator has reviewed it. The implementation is proprietary and not published; verification rests on signed data.

1. Verify a recorded fault test

A disposable twin cluster was run through: commit with 4 nodes, crash 1 then commit with 3, crash 2 (no commit), restarts. The recording is signed data. Verify it, then tamper with it and watch verification fail.

2. Live test-cluster state proofs

Four nodes of the running test cluster each sign a state proof. Your browser verifies the four signatures and checks that they agree.

3. Sandbox: send requests, crash nodes, verify the result

A dedicated sandbox twin (own keys, own state). Crash up to 2 nodes: with 3 up a request still commits; with only 2 up it must not. Nodes you leave down are restarted automatically after 2 minutes. A restarted node catches up when the next request commits.

Send an authorization request

Fault injection

ready

Other ways to verify

Machine-readable recipes: AI_VERIFY.json. Standalone verifiers import nothing from CAIN. Everything here is PRE-PRODUCTION and same-author.