Crypto Audit: evidence, proof and selling tools

Official CAIN-42 IHVRK · New to this product? Learn it first

Don't trust CAIN-42. Verify CAIN-42. This is the Independent Human Verification Resource Kit for Crypto Audit: every claim its page makes, as the exact request and the answer it must give, recorded live and signed. You check it on your own machine with a short Python script that uses no CAIN-42 code.

Every claim matched when recorded

Download the kit (.zip)

Everything you can give a customer

Selling tools

Pitch, emails, call script, objection answers, one-page summary, proposal.

Evidence pack

The figures and a ready email to an auditor or security reviewer.

Answers to buyer questions

Paste into a security questionnaire: YES, PARTIAL, NO or ASK.

Figures & benchmarks

Every number from the signed record, ready for a spreadsheet.

The kit

Kit	`crypto-audit-20261103T224839`
Recorded	2026-11-03T22:48:39+00:00 against cainstudio.online
Claims	6
Zip SHA-256	`637ba65f2cdb8665908177901e8b053a7e6eaf1cb79ec93b1574c1e412a24053` (also in SHA256SUMS)
Signing key fingerprint	`1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3`, published on cainstudio.online · mcpgate.online · clawx.click

Verify it on your own machine

unzip cain42-ihvrk-crypto-audit.zip && cd cain42-ihvrk-crypto-audit
python3 verify.py            # offline: hashes, Ed25519 signature, recorded answers
python3 verify.py --live     # also re-send every request yourself and check the answers now

A claim that cannot be checked counts as a FAIL, never a pass. The live check is the one that depends on nothing we recorded.

The claims in this kit

#	Claim	Answer must contain
C01	Modern code: bcrypt, SHA-256, secrets, default TLS -> No findings: no false alarm.	`[0]`
C02	Signature check off, TLS check off, key in the code -> Three classic mistakes, three findings.	`[3]`
C03	Passwords hashed with MD5 -> MD5 is broken for passwords.	`["WeakHash_MD5"]`
C04	AES in ECB mode -> ECB leaks patterns in the data.	`["InsecureMode_ECB"]`
C05	random() used for a security token -> random() is predictable; use secrets.	`["InsecureRandom_Crypto"]`
C06	A 1024-bit RSA key -> Under 2048 bits is too short.	`["ShortRSAKey"]`

Evidence links you can give your customers

Kit download: /proof/bundle/ihvrk-kits/cain42-ihvrk-crypto-audit.zip
Each file on its own: README.txt · claims.json · transcript.json · MANIFEST.json · MANIFEST.sig · kit-key.json · verify.py
Run the live demo yourself on any of the three sites: cainstudio.online · mcpgate.online · clawx.click
The product explained: /guide-crypto-audit.html · what it does not do: limits
Signing key on three independent domains: cainstudio.online · mcpgate.online · clawx.click
Three ready-to-send evidence pages: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks
Every kit: all IHVRKs · machine-readable index

Send this to your customer

Don't take our word for it. Verify Crypto Audit yourself:
1. Download the official CAIN-42 IHVRK: https://cainstudio.online/proof/bundle/ihvrk-kits/cain42-ihvrk-crypto-audit.zip
   SHA-256: 637ba65f2cdb8665908177901e8b053a7e6eaf1cb79ec93b1574c1e412a24053
2. Unzip it and run: python3 verify.py --live   (Python 3, standard library only, no account)
3. Check the signing key fingerprint 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3
   matches https://cainstudio.online/evidence-kit-key.json, https://mcpgate.online/evidence-kit-key.json and https://clawx.click/evidence-kit-key.json
Live demo: https://cainstudio.online/guide-crypto-audit-lab.html
What it does not do: https://cainstudio.online/guide-crypto-audit-limits.html

What this kit is, and is not

It shows what the live product answered to these inputs, and lets anyone check that again. It is not a third-party audit, a certification, or a promise about inputs not listed. The product's limits page lists what it does not do.