HackerTrans
TopNewTrendsCommentsPastAskShowJobs

kennmangum

no profile record

Submissions

Cryptographic Receipts for AI Inference

six-sov.com
2 points·by kennmangum·4 mesi fa·2 comments

Sovereign memory for AI agents – persistent state with cryptographic receipts

memory.six-sov.com
1 points·by kennmangum·4 mesi fa·2 comments

Cryptographic receipts for LLM inference – verify your AI in 30 seconds

npmjs.com
1 points·by kennmangum·5 mesi fa·1 comments

comments

kennmangum
·4 mesi fa·discuss
We built a receipt system for AI inference — every response gets a SHA-256 hash, Schnorr signature, and optional XRPL anchor.

The problem: enterprise AI deployments need audit trails that can't be edited. Database logs don't cut it for regulated industries.

Try it: npx six-verifier verify <hash>

Looking for feedback from folks building compliance-sensitive AI applications.
kennmangum
·4 mesi fa·discuss
[dead]
kennmangum
·4 mesi fa·discuss
Agents get durable memory across sessions. Every write produces a cryptographic receipt. You can verify, export, or delete anytime. No vendor lock-in.

Happy to answer questions on architecture, crypto choices, or why "agentic memory" is a real category.
kennmangum
·5 mesi fa·discuss
Verify an inference in 30 seconds: npx six-verifier sample-receipt.json The receipt proves: who ran it, what model, when, and that the output wasn't tampered with. Not "trust our logs" — actual cryptographic proof. Signed receipts + Merkle attestations. More at: https://six-sov.com Happy to answer technical questions — threat model, crypto choices, performance tradeoffs.