Black Box flight recorder: figures & benchmarks

Evidence for Black Box flight recorder: 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

attack cases refused or flagged as claimed

258 ms

median round trip (min 35, max 1519), incl. network

#	Kind	Claim	Recorded value	HTTP	ms
C01	control	Record, seal, verify -> A sealed recording verifies.	`true`	200	254
C02	attack	Edit an event after sealing -> Changing one event changes its hash and the root.	`false`	200	377
C03	attack	Drop an event after sealing -> Truncation is detected.	`false`	200	1519
C04	attack	Add an event after sealing -> A sealed recording accepts nothing more.	`"HTTP 409"`	409	258
C05	attack	Inclusion proof against a made-up root -> A proof must lead to the root it claims.	`false`	200	35

Copy the table (paste into a spreadsheet)

id	kind	claim	recorded_value	expected	http	ms	recorded_at
C01	control	Record, seal, verify -> A sealed recording verifies.	true	[true]	200	254	2026-11-03T22:45:59+00:00
C02	attack	Edit an event after sealing -> Changing one event changes its hash and the root.	false	[false]	200	377	2026-11-03T22:46:00+00:00
C03	attack	Drop an event after sealing -> Truncation is detected.	false	[false]	200	1519	2026-11-03T22:46:02+00:00
C04	attack	Add an event after sealing -> A sealed recording accepts nothing more.	"HTTP 409"	[]	409	258	2026-11-03T22:46:02+00:00
C05	attack	Inclusion proof against a made-up root -> A proof must lead to the root it claims.	false	[false]	200	35	2026-11-03T22:46:03+00:00

Download: figures.tsv · transcript.json (full answers) · whole kit

How to read these numbers

Recorded 2026-11-03T22:46:03+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.