CAIN-42 MCPGateDaily Evidence
CAIN-42 is a Byzantine trust fabric. Every 30 minutes, each of its two live validator clusters commits a real write through PBFT. A signed proof of it, linked to the proof before it by hash, is published here. Once a day the newest proof of each chain is recorded in Sigstore Rekor, a public append-only log that FIRME AI CORPORATION does not run. After that, no one, including us, can change or backdate any earlier proof without it showing. Everything below comes from the live files, and failures are shown as they are.
1. Today's public anchors
The anchored proof commits to every proof before it. Open the Rekor entry yourself: it is served by Sigstore, not by us.
Loading…
2. Re-check it in your browser
Downloads each chain's index and its newest proofs. It recomputes every hash with your browser's own SHA-256, checks each link to the previous proof, and checks that the anchored proof is still in the chain unchanged. Nothing is sent anywhere.
3. Today's work
Loading…
4. Full history, day by day
Every day since the first proof. Each count comes from the signed chain indexes. "Not operational" means the write did not commit, its certificate did not verify, or the replicas disagreed. Those proofs stay in the chain.
| Day (UTC) | cain-mr-01 proofs | operational | cain-mr-02 proofs | operational | Rekor anchor |
|---|---|---|---|---|---|
| Loading… | |||||
5. Verify everything yourself
Python 3.8+, standard library only, no CAIN code. It fetches the Rekor entry directly from Sigstore:
curl -fsSLO https://clawx.click/evidence/daily-anchor/verify_daily_anchor.py python3 -I verify_daily_anchor.py --chain hourly-proof --trust-anchor t1I4vBpOasgbBSWYTN2g7xL1En7qZ6lhgbt6n2OpeG8= --all --full-chain python3 -I verify_daily_anchor.py --chain hourly-proof-mr02 --trust-anchor t1I4vBpOasgbBSWYTN2g7xL1En7qZ6lhgbt6n2OpeG8= --all --full-chain
Re-check every proof's quorum certificate (3 of 4 validator signatures) with the clean-room verifier:
B=https://clawx.click/evidence/hourly-proof/
curl -so verify_hourly_proofs.py "${B}verify_hourly_proofs.py.txt"
curl -so verify_pbft_qc_bundle.py "${B}verify_pbft_qc_bundle.py.txt"
python3 verify_hourly_proofs.py "$B" --pin t1I4vBpOasgbBSWYTN2g7xL1En7qZ6lhgbt6n2OpeG8=
The trust anchor is the CAIN-42 evidence-root key. Get it from a source you trust: it is also published at cainstudio.online, mcpgate.online and clawx.click. Compare all three.
What this proves, and what it does not
- Proves: each anchored chain existed, unchanged, no later than the Rekor time. Every proof since is hash-linked to it.
- Proves: each OPERATIONAL proof's write was committed with a certificate signed by at least 3 of the 4 pinned validator keys. You can re-check it with the clean-room verifier above.
- Does not prove: who holds the keys. All validators and the evidence-root key are operated by the same three-person team at FIRME AI CORPORATION. The quorum tolerates one faulty validator; it is not independent of its operator.
- Does not prove: that a proof's measurements are true. It proves the proof was not changed later. No third-party audit has been completed, and no 72-hour soak has passed yet.
- Anchoring began on 2026-11-02. Proofs before that date are covered by the first anchor only from that day on.