I’ve been working on a protocol for a bit now and have just released a whitepaper with the implementation on GitHub. It’s a spec and reference implementation for a coordination layer where every message is signed, every state change is hash-chained into an audit log, and a privacy guarantee is enforced by routing precedence rather than by policy. There’s an optional ZK principal-attestation primitive (heavy handshake vs. default Apache 2.0) in the spec. The handshake (capability intersection) is a setup step; the audit log is what the protocol actually delivers. The protocol is not agent-specific , but a motivating use case is auditing how autonomous agents operate; the audit log gives the verifier the same answer the operator gets; any cross-organizational service coordination is in scope. Five invariant(s) at the core: Every message is signed (Ed25519 over canonical JSON, RFC 8785) Every session has a capability-intersecting handshake Every state change produces a hash-chained audit entry Principal identity is attested by a use-once ZK proof, not transmitted Personal data is forced local by routing precedence (the first thing the router checks - no override) Spec (CC BY 4.0): https://github.com/githubscum/aip-protocol/blob/v1.1.0/docs/aip-v1.0-spec.md Whitepaper (CC BY 4.0): https://github.com/githubscum/aip-protocol/blob/v1.1.0/docs/AIP-whitepaper.md Reference implementation (Apache 2.0): https://github.com/githubscum/aip-protocol Cite (Zenodo DOI): https://doi.org/10.5281/zenodo.21267380 Bitcoin-anchored OTS chain: whitepaper, spec, release tarball, and v1.1.0 commit SHA-256 all attested in Bitcoin blocks 957210–957217 (mined 2026-07-08). See dev-logs/ots/ in the repo. Author (ORCID): https://orcid.org/0009-0006-2476-1615 Looking for feedback on the wire format, the audit chain, and the routing precedence rules, thanks for taking the time! submitted by /u/rredditscum
Originally posted by u/rredditscum on r/ArtificialInteligence