Quorum-QaaS × KEYSTONE: every signed fix, committed by a Byzantine quorum

KEYSTONE, the CAIN-42 product that finds, fixes and proves code defects, was the first customer of Quorum-QaaS. Each of its 8 signed ledger records was sent to Quorum-QaaS as a SHA-256 digest, ordered and committed by the live 4-replica PBFT cluster cain-mr-02 with at least 3 of 4 replicas signing, and its receipt was checked by the standalone verifier with no CAIN code.

Result: PASS — 15 of 15 checks passed. Membership hash 9ad62c270187b9e16d2938370457ddc257cdf9849be61253f4319a5738387fd2.

Every KEYSTONE record

KEYSTONE #	KEYSTONE verdict	record hash	cluster sequence	signers	standalone verifier
0	NOT_VERIFIED	`004e92d9c27ae51a…`	360157	3 of 4	NOTARIZED
1	VERIFIED_FIX	`5239666159b3d5df…`	360159	3 of 4	NOTARIZED
2	VERIFIED_FIX	`67def5455ef614dd…`	360161	3 of 4	NOTARIZED
3	VERIFIED_FIX	`60b64ecb238343bf…`	360163	3 of 4	NOTARIZED
4	NOTHING_TO_FIX	`fd5bfacc094630bd…`	360167	3 of 4	NOTARIZED
5	NOT_VERIFIED	`a1bc30b0789959bc…`	360172	3 of 4	NOTARIZED
6	VERIFIED_FIX	`d4a6727a8801a606…`	360174	3 of 4	NOTARIZED
7	VERIFIED_FIX	`b0366701c7271ccd…`	360176	3 of 4	NOTARIZED

Every check

PASS — KEYSTONE ledger verifies (8 signed records)
PASS — membership hash matches what the replicas report
PASS — KEYSTONE record #0 (NOT_VERIFIED) notarized + verified standalone
PASS — KEYSTONE record #1 (VERIFIED_FIX) notarized + verified standalone
PASS — KEYSTONE record #2 (VERIFIED_FIX) notarized + verified standalone
PASS — KEYSTONE record #3 (VERIFIED_FIX) notarized + verified standalone
PASS — KEYSTONE record #4 (NOTHING_TO_FIX) notarized + verified standalone
PASS — KEYSTONE record #5 (NOT_VERIFIED) notarized + verified standalone
PASS — KEYSTONE record #6 (VERIFIED_FIX) notarized + verified standalone
PASS — KEYSTONE record #7 (VERIFIED_FIX) notarized + verified standalone
PASS — resubmitting the same request is idempotent (same cluster sequence)
PASS — reusing a request_id for a different digest is refused
PASS — a KEYSTONE record edited after notarization fails against its receipt
PASS — a receipt checked against the wrong cluster pin fails
PASS — cluster application state unchanged by notarization (read-only for customers)

Commit time per record: median 12354 ms (min 4367, max 56683).

Verify it yourself

Quorum-QaaS x KEYSTONE, 20261015T191631Z

KEYSTONE's signed fix ledger was the first customer of Quorum-QaaS: every record_hash was ordered and
committed by the live 4-replica PBFT cluster cain-mr-02 (quorum 3 of 4), and every receipt was
checked by the standalone verifier in an isolated interpreter.

Result: PASS, 15/15 checks.

Verify it yourself (Python 3.8+, pip install cryptography, no CAIN code):
  B=https://clawx.click/evidence/quorum-qaas-keystone-2026-10-15/
  curl -so verify_bundle.py "${B}verify_bundle.py.txt"
  python3 verify_bundle.py "$B" --pin "$(curl -s 'https://cainstudio.online/api/v1/live-cluster/membership?cluster=cain-mr-02' | python3 -c 'import json,sys;print(json.load(sys.stdin)["configuration_hash"])')"

Files: report.json, MANIFEST.json (signed: MANIFEST.sig.json), receipts, verify_bundle.py, verify_qaas_receipt.py, verify_pbft_qc_bundle.py.