kennmangum

4 ms·

1. 1.▲
   Cryptographic Receipts for AI Inference(six-sov.com)

   2 points by kennmangum 7mo ago|2 comments
2. 2.▲
   by kennmangum 7mo ago

   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 i
3. 3.▲
   Sovereign memory for AI agents – persistent state with cryptographic receipts(memory.six-sov.com)

   1 points by kennmangum 7mo ago|2 comments
4. 4.▲
   by kennmangum 7mo ago

   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&qu
5. 5.▲
   Cryptographic receipts for LLM inference – verify your AI in 30 seconds(npmjs.com)

   1 points by kennmangum 7mo ago|1 comments
6. 6.▲
   by kennmangum 7mo ago

   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 r