CAIN-42 MCPGate

CAIN-42 evidence library

PROOFLOOP LIVE signed evidence

Evidence bundle: 0 claims, 0 of 0 invariants held.

Last reviewed 2026-11-19

Browse the raw bundle · SHA-256 manifest

The bundle's own README

PROOFLOOP LIVE signed evidence#

Our own live evidence, not a third-party audit. report.md and findings.json are bound to the signed record; every extra file is named with its SHA-256 in the signed findings.

Verify it yourself (no CAIN code required)#

You must pin the signing key yourself. Do not trust public_key.json in this folder on its own: anyone who can hand you this zip could have replaced that file and re-signed every record. Fetch the key from the issuer:

pip install cryptography KEY=$(curl -s https://cainstudio.online/keystone/public-key | python3 -c 'import json,sys; print(json.load(sys.stdin)["public_key_b64"])') python3 verify_keystone.py --pinned-pub "$KEY"

or compare fingerprints out of band and pin by fingerprint:

python3 verify_keystone.py --pinned-fingerprint SHA256:2232b4add9b35d4016e5be270df4ed56e0dc9b39a0530ac69891073253aae90d

Run with no pin and the verifier refuses (exit code 3). With a pin it recomputes every record's SHA-256 content hash, checks every Ed25519 signature against YOUR key, checks the chain links and artifact digests, and checks head.json (signed by the same key) lists exactly the records in this folder, in order. Change any byte, swap the key, or remove, add or reorder a record and it prints TAMPERED OR INVALID.

The signing key's fingerprint at the time this bundle was made: SHA256:2232b4add9b35d4016e5be270df4ed56e0dc9b39a0530ac69891073253aae90d.

Try CAIN-42 on your own agents

Create a free account and every new account starts with a 30-day trial of the full platform. Or try the sandbox first, with no account at all.

Create a free account →  ·  Try the sandbox  ·  See the whole ecosystem