News for hackers. Stuff that matters.

rmasoodx22

Every AI-assisted code change in our pipeline produces a receipt — a signed, chained, Merkle-anchored JSON artifact proving what was evaluated, what verdict was reached, and that the record hasn't been altered.

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.

PyPI: https://pypi.org/project/titan-gate/

Nice protocol design — the "absence of signature is itself evidence" framing is exactly right. Oath solves the authorization layer: did a human approve this action before it ran. Titan Gate sits one layer up: did the AI-written code that resulted from those actions get cryptographically receipted before it shipped. The two compose cleanly. Oath attests the human intent. Titan Gate receipts the code change that follows. Both are needed for a complete audit trail in a SOC2 environment. Our receipt model: every PR gets HMAC-SHA256 signed, Merkle-ledgered, with SOC2 control mappings (CC6/CC7/CC8) embedded in the receipt JSON. The receipt travels with the code. Verify command: pip install titan-gate titan verify receipt.json --key 0dd06d207d711486523b21fe027681d05fc13c10ac313d979fc1e7de657d2447 Live receipt from today: 89bd57ed-b7e1-455a-9f63-5d0005d8d27f On your protocol design — the namespace:action:scope format looks solid. One edge case worth considering: replay attacks where a valid attestation for action A gets reused for a structurally identical action A'. How are you scoping attestations to a specific execution context rather than just action class? https://github.com/Rehanrana11/titan-gate
Interesting timing — we just shipped something adjacent but targeting a different layer. Veracity seems focused on dataset integrity for training data. Titan Gate sits at the code change layer — every AI-assisted PR gets a cryptographic receipt: HMAC-SHA256 signed, Merkle-ledgered, SOC2 control mappings (CC6/CC7/CC8) embedded. The receipt travels with the code. Any engineer can verify independently: pip install titan-gate titan verify receipt.json --key 0dd06d207d711486523b21fe027681d05fc13c10ac313d979fc1e7de657d2447 Live receipt from today: 89bd57ed-b7e1-455a-9f63-5d0005d8d27f Curious how you're handling the code change audit layer — are your users asking about that too, or purely dataset provenance? The two problems seem complementary rather than overlapping. https://github.com/Rehanrana11/titan-gate
Update: ran it on its own repo just now.

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

Actions: https://github.com/Rehanrana11/titan-gate/actions

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&#39;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...

( Read More... | 1 comment | on HN )