AC2 Protocol: The missing security layer for AI agents
josephcecala
16 points
14 comments
August 27, 2026
Related Discussions
Found 5 related stories in 69.0ms across 4,692 title embeddings via pgvector HNSW
- How to disable or avoid intrusive AI ColinWright · 276 pts · August 17, 2026 · 51% similar
- The AI risk is inside the labs mirzap · 41 pts · July 28, 2026 · 51% similar
- It's not a "rogue AI" when a badly made security harness executes scripts doener · 32 pts · July 22, 2026 · 51% similar
- Agent-talk: Enabling coding agents to work together xhluca · 48 pts · July 16, 2026 · 49% similar
- Collaborative Human Agent Protocol (CHAP) arsalanshahid · 24 pts · August 19, 2026 · 49% similar
Discussion Highlights (5 comments)
josephcecala
AC2 is an open standard that puts users back in control of AI-driven signing operations, providing verifiable proof of intent and credential isolation. The problem: a compromised agent runtime (e.g. a malicious plugin dependency) can leak everything injected into it like API keys or session tokens, and there's no way to prove whether a human actually approved what happened, since chat-based "approvals" are just messages, spoofable and session-hijackable. AC2 closes both gaps. Approvals become a FIDO2 passkey signature from your device, that's hardware-bound, phishing-resistant, and a real audit trail instead of a chat message. And credentials never enter the runtime at all: the agent gets a signed authorization, not the key. Compromise the runtime, there's nothing to steal. Under the hood: AC2 opens a direct, end-to-end encrypted WebRTC connection between a user's wallet and an agent. When the agent needs to sign something (a payment, a commit, an API call), it sends the request via AC2, the user approves from their own wallet, and the signature is delegated back. The private key never leaves the user's device. Built on three open standards: DIDComm v2.0 (messaging), WebAuthn/FIDO2 (hardware-bound auth), and WebRTC DataChannel (P2P transport, no relay servers). Lightweight (~50 lines for a basic flow), blockchain-agnostic, and works alongside your existing setup. One plugin, one command. Built by the Algorand Foundation team behind Pera Wallet, Rocca, Intermezzo, and LiquidAuth. Use cases include code deploys, client comms, API access, x402 payments, and intent-based delegation via AP2 IntentMandates. Spec is live and open. Reference implementation (AC2 Wallet) is on GitHub, Play Store, and App Store, with a plugin to try the full flow. This is v1, feedback welcome.
semiquaver
I can’t help but see the crypto stink all over this and recoil. This is just trying to salvage ideas and tools from the last fad into the current one. Seems like “ask for approval, except you approve by spending a little of some random altcoin” > Disclaimer: AC2 is a self-custodial Algorand wallet. You — and only you — hold your seed phrase, your keys, and your crypto-assets on your own device. Pera Wallet, Lda does not hold, custody, or have access to your seed phrase, your keys, or your crypto-assets, and cannot recover them on your behalf.
nekusar
Yeah, so its some shitcoin vehicle with word-slop. /ignore
motohagiography
Regardless of what people think of blockchains, it's the necessary foundation for any agent governance. If not this protocol, then something in this direction. The analogy I would use is the only thing reliably containing humanity is interstellar distances, and the equivalent for ASI would be cryptographic distances, where the only way to relate to anything safely will be via a crypto interface. Compute is the physics of an ASI's substrate, and cryptography is the only meaningful barrier we've been able to create in it so far.
chrisjj
> You need sovereignty. You keep using that word. I do not think it means what you think it means.