rmasoodx22
Verify one now:
pip install titan-gate
titan-verify receipt.json --key <hex_key>
No network. No database. No trusted third party.Real example receipt (test key is 64 zeros): https://github.com/Rehanrana11/titan-gate-demo/blob/main/.ti...
The format is TRS-1 (Titan Receipt Standard). Full cryptographic spec: https://github.com/Rehanrana11/titan-gate-public/blob/main/S...
Receipts chain via prev_receipt_hash. Daily batches are Merkle-aggregated and anchored as files in Git — tamper-evidence without a blockchain.
SOC2 angle: auditors verify CC6/CC7/CC8 controls from the receipt alone, no infrastructure access required.
Show HN: cryptographic receipts for AI code changes pip install titanate
PR opened → evaluated → receipt generated → artifact uploaded in 27s.
Real receipt from the run: receipt_id: e0c5de94-be7a-4586-9a7f-98eb... tenant_id: Rehanrana11 repo: Rehanrana11/titan-gate HMAC-SHA256 signed, chained, verifiable
Show HN: Titan Gate – cryptographic receipts for AI-assisted code changes
https://github.com/Rehanrana11/titan-gate
AI writes code fast. SOC2 auditors ask: how do you know what changed, who approved it, and that the record wasn't altered?Titan Gate answers with cryptographic receipts — not process docs.Every PR gets evaluated by a three-judge engine (structural, semantic, policy), scored, signed with HMAC-SHA256, chained to the previous receipt, and stored at .titan/receipts/ in your repo.Any engineer...