Tamper-evident audit trail for AI coding agent activity
SHA-256 hash chains and SMT proofs make AI agent logs actually verifiable.
Headless browser with SHA-256 hash chain + Ed25519 audit trails. MCP server for AI agents. Stealth. Self-verifiable proof bundles. Powers the SwarmSync.ai agent marketplace.
Cryptographic proof bundles for AI agent browser actions—screenshots can be faked, hash chains can't.
AI agent developers, compliance teams, security researchers
Playwright · Puppeteer · Browserbase
So I built Conduit. It's a headless browser (Playwright under the hood) that records every action into a SHA-256 hash chain and signs the result with Ed25519. Each action gets hashed with the previous hash, forming a tamper-evident chain. At the end of a session, you get a "proof bundle" -- a JSON file containing the full action log, the hash chain, the signature, and the public key. Anyone can independently verify the bundle without trusting the party that produced it.
The main use cases I'm targeting:
- *AI agent auditing* -- You hand an agent a browser. Later you need to prove what it did. Conduit gives you cryptographic receipts. - *Compliance automation* -- SOC 2, GDPR data subject access workflows, anything where you need evidence that a process ran correctly. - *Web scraping provenance* -- Prove that the data you collected actually came from where you say it did, at the time you say it did. - *Litigation support* -- Capture web content with a verifiable chain of custody.
It also ships as an MCP (Model Context Protocol) server, so Claude, GPT, and other LLM-based agents can use the browser natively through tool calls. The agent gets browse, click, fill, screenshot, and the proof bundle builds itself in the background.
Free, MIT-licensed, pure Python. No accounts, no API keys, no telemetry.
GitHub: https://github.com/bkauto3/Conduit
Install: `pip install conduit-browser`
Would love feedback on the proof bundle format and the MCP integration. Happy to answer questions about the cryptographic design.
SHA-256 hash chains and SMT proofs make AI agent logs actually verifiable.
SHA-256 hash chains for AI audit trails—solves EU AI Act compliance elegantly.
SHA-256 hash-chained AI audit log, but only 9 commits and ko-fi upsell.
Hash chaining before write beats S3 Object Lock for pre-write tampering protection.
Cryptographic hash chains make agent action logs legally defensible—LangSmith and Langfuse don't do this.
Cryptographic hash chains make AI agent logs legally defensible when LangSmith can't.