CAIN-42 MCPGate
42CAIN-42 IHVRK › Taloscrypt Keymgmt › 3. Figures

Taloscrypt Keymgmt: figures & benchmarks

Evidence for Taloscrypt Keymgmt: 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.

4/4

claims matched when recorded

0

attack cases: this kit records normal requests only

0 ms

median round trip (min 0, max 1), incl. network

#KindClaimRecorded valueHTTPms
C01controltaloscrypt-keymgmt (catalog service): the demo completes (ok) -> ok = every step succeeded; refused = the service answered and refused a step, as this demo shows on purpose."ok"2000
C02controlStep 1: POST /v1/keys answers HTTP 200 -> This step succeeded in the reference run.2002001
C03controlStep 2: POST /v1/keys/demo-bad9dae9/rotate answers HTTP 200 -> This step succeeded in the reference run.2002000
C04controlStep 3: GET /v1/keys/demo-bad9dae9 answers HTTP 200 -> This step succeeded in the reference run.2002000

Copy the table (paste into a spreadsheet)

id	kind	claim	recorded_value	expected	http	ms	recorded_at
C01	control	taloscrypt-keymgmt (catalog service): the demo completes (ok) -> ok = every step succeeded; refused = the service answered and refused a step, as this demo shows on purpose.	"ok"	["ok"]	200	0	2026-11-03T23:29:20+00:00
C02	control	Step 1: POST /v1/keys answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	1	2026-11-03T23:29:20+00:00
C03	control	Step 2: POST /v1/keys/demo-bad9dae9/rotate answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:21+00:00
C04	control	Step 3: GET /v1/keys/demo-bad9dae9 answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:21+00:00

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

How to read these numbers