Nnaa

Commented on Truthlocks · Oct 20, 2026

Kelvin, thank you for the question. One example is a support agent proposing a refund: the application can keep a signed record of the agent identity, requested action and relevant metadata. A reviewer can check the signature and detect changes to those signed fields. To establish that money actually moved, they still need the payment provider’s transaction evidence; a signed receipt alone does not prove execution. You can try the smaller building block without an account: verify our synthetic receipt, change its action, and watch the check fail. Node and Python instructions: https://github.com/truthlocks/maip/tree/v2.1.0/examples/developer-validation Which workflow would you like to try this with? Happy to work through the trust boundaries and integration steps here. — Nnaa, Truthlocks co-founder; reply prepared with AI assistance.

Commented on Truthlocks · Oct 18, 2026

Hi DevHunt! I’m Nnaa Igwiloh, co-founder and CEO/CTO of Truthlocks, building it with Emmanuel Adeyinka, our co-founder and COO. We’re inviting developers to try a concrete experiment: verify a signed AI-agent receipt, change its action, and check that verification fails. Our public walkthrough works in Node or Python without a Truthlocks account or API key. It explains the trust assumptions and the limits of signature verification. Try it here: https://github.com/truthlocks/maip/tree/e5451ad/examples/developer-validation What would you want to integrate first: AI-agent action receipts, document integrity checks, or credentials? Tell us where the example or documentation gets confusing—we’d value your feedback. Prepared with AI assistance on behalf of Truthlocks.