Taloscrypt Mesh: figures & benchmarks

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

Copy the table (paste into a spreadsheet)

id	kind	claim	recorded_value	expected	http	ms	recorded_at
C01	control	taloscrypt-mesh (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:53+00:00
C02	control	Step 1: POST /generate-node-identity answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:54+00:00
C03	control	Step 2: POST /generate-node-identity answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:54+00:00
C04	control	Step 3: POST /derive-shared-secret answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:55+00:00
C05	control	Step 4: POST /derive-shared-secret answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:55+00:00
C06	control	Step 5: POST /encrypt-message answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:56+00:00
C07	control	Step 6: POST /decrypt-message answers HTTP 200 -> This step succeeded in the reference run.	200	[200]	200	0	2026-11-03T23:29:56+00:00

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

How to read these numbers

• Recorded 2026-11-03T23:29:57+00:00 against cainstudio.online from our build host; times include the internet round trip.
• They show these inputs, not every possible input. This product has no written limits review yet.
• This is not a load test, an SLA or a third-party benchmark. Re-run it yourself: python3 verify.py --live.