CAIN-42 CAIN StudioQuorum-QaaS (4-region PBFT): figures & benchmarks
Evidence for Quorum-QaaS (4-region PBFT): 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks · 4. Selling tools · IHVRK kit · Learn it · why these pages exist
Every number on this page is read from the signed transcript inside the IHVRK kit; none is typed in by hand.
9/9
claims matched when recorded
8
attack cases refused or flagged as claimed
110 ms
median round trip (min 87, max 140), incl. network
| # | Kind | Claim | Recorded value | HTTP | ms |
|---|---|---|---|---|---|
| C01 | control | Published receipt verifies -> Signed by a quorum of the pinned cluster. | "NOTARIZED" | 200 | 109 |
| C02 | attack | Digest changed -> The quorum signed this digest, not yours. | "NOT_VERIFIED" | 200 | 140 |
| C03 | attack | Cluster renamed (unsigned top-level field) -> cluster_id must equal the signed membership's; the 2026-11-03 lab found the verifier echoing it. Fixed and deployed 2026-11-03. | "NOT_VERIFIED" | 200 | 132 |
| C04 | attack | Request id swapped -> The commit certificate names exactly one request. | "NOT_VERIFIED" | 200 | 126 |
| C05 | attack | Sequence moved -> The certificate is for one slot in the log. | "NOT_VERIFIED" | 200 | 110 |
| C06 | attack | Operation digest differs from the receipt digest -> The operation must notarize exactly the receipt's digest. | "NOT_VERIFIED" | 200 | 106 |
| C07 | attack | Commit signatures dropped to one -> One replica is not a quorum (needs 3 of 4). | "NOT_VERIFIED" | 200 | 125 |
| C08 | attack | Wrong pin (another cluster's configuration) -> Pinned to a configuration this receipt was not signed by. | "NOT_VERIFIED" | 200 | 92 |
| C09 | attack | Commit certificate removed -> No commit quorum, no notarization. | "NOT_VERIFIED" | 200 | 87 |
Copy the table (paste into a spreadsheet)
id kind claim recorded_value expected http ms recorded_at C01 control Published receipt verifies -> Signed by a quorum of the pinned cluster. "NOTARIZED" ["NOTARIZED"] 200 109 2026-11-03T22:47:17+00:00 C02 attack Digest changed -> The quorum signed this digest, not yours. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 140 2026-11-03T22:47:17+00:00 C03 attack Cluster renamed (unsigned top-level field) -> cluster_id must equal the signed membership's; the 2026-11-03 lab found the verifier echoing it. Fixed and deployed 2026-11-03. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 132 2026-11-03T22:47:18+00:00 C04 attack Request id swapped -> The commit certificate names exactly one request. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 126 2026-11-03T22:47:19+00:00 C05 attack Sequence moved -> The certificate is for one slot in the log. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 110 2026-11-03T22:47:19+00:00 C06 attack Operation digest differs from the receipt digest -> The operation must notarize exactly the receipt's digest. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 106 2026-11-03T22:47:20+00:00 C07 attack Commit signatures dropped to one -> One replica is not a quorum (needs 3 of 4). "NOT_VERIFIED" ["NOT_VERIFIED"] 200 125 2026-11-03T22:47:21+00:00 C08 attack Wrong pin (another cluster's configuration) -> Pinned to a configuration this receipt was not signed by. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 92 2026-11-03T22:47:21+00:00 C09 attack Commit certificate removed -> No commit quorum, no notarization. "NOT_VERIFIED" ["NOT_VERIFIED"] 200 87 2026-11-03T22:47:22+00:00
Download: figures.tsv · transcript.json (full answers) · whole kit
How to read these numbers
- Recorded 2026-11-03T22:47:22+00:00 against cainstudio.online from our build host; times include the internet round trip.
- They show these inputs, not every possible input. Known misses are on the limits page.
- This is not a load test, an SLA or a third-party benchmark. Re-run it yourself:
python3 verify.py --live.