FrontierGuard: figures & benchmarks
Evidence for FrontierGuard: 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.
3/3
claims matched when recorded
2
attack cases refused or flagged as claimed
170 ms
median round trip (min 154, max 4675), incl. network
| # | Kind | Claim | Recorded value | HTTP | ms |
|---|---|---|---|---|---|
| C01 | control | A small start-up -> Far below every threshold. | false | 200 | 4675 |
| C02 | attack | $250M compute, $2B revenue -> Above the thresholds. | true | 200 | 170 |
| C03 | attack | $150M compute, $100M revenue -> The compute-spend test alone is enough. | true | 200 | 154 |
Copy the table (paste into a spreadsheet)
id kind claim recorded_value expected http ms recorded_at C01 control A small start-up -> Far below every threshold. false [false] 200 4675 2026-11-03T22:51:43+00:00 C02 attack $250M compute, $2B revenue -> Above the thresholds. true [true] 200 170 2026-11-03T22:51:43+00:00 C03 attack $150M compute, $100M revenue -> The compute-spend test alone is enough. true [true] 200 154 2026-11-03T22:51:44+00:00
Download: figures.tsv · transcript.json (full answers) · whole kit
How to read these numbers
- Recorded 2026-11-03T22:51:44+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.