CAIN RIG: figures & benchmarks
Evidence for CAIN RIG: 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.
5/5
claims matched when recorded
4
attack cases refused or flagged as claimed
65 ms
median round trip (min 50, max 95), incl. network
| # | Kind | Claim | Recorded value | HTTP | ms |
|---|---|---|---|---|---|
| C01 | control | Use the token once -> Valid, first use. | true | 200 | 65 |
| C02 | attack | Use the same token twice -> Single use: the second is refused. | false | 200 | 73 |
| C03 | attack | A thief uses the token with another key -> No matching private key. | false | 200 | 95 |
| C04 | attack | Use a 'read' token to delete -> Wrong action. | false | 200 | 57 |
| C05 | attack | Register a child agent with more rights than its parent -> Delegation can only narrow. | true | 200 | 50 |
Copy the table (paste into a spreadsheet)
id kind claim recorded_value expected http ms recorded_at C01 control Use the token once -> Valid, first use. true [true] 200 65 2026-11-03T22:54:40+00:00 C02 attack Use the same token twice -> Single use: the second is refused. false [false] 200 73 2026-11-03T22:54:41+00:00 C03 attack A thief uses the token with another key -> No matching private key. false [false] 200 95 2026-11-03T22:54:41+00:00 C04 attack Use a 'read' token to delete -> Wrong action. false [false] 200 57 2026-11-03T22:54:42+00:00 C05 attack Register a child agent with more rights than its parent -> Delegation can only narrow. true [true] 200 50 2026-11-03T22:54:42+00:00
Download: figures.tsv · transcript.json (full answers) · whole kit
How to read these numbers
- Recorded 2026-11-03T22:54:43+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.