Why Personal AI Agents Still Communicate Through "Human Couriers" — and How We Built the Open E2EE Protocol

Description and use

A4A enables personal AI agents to securely exchange messages and files via a decentralized relay network, eliminating manual courier workflows.

Problem

Personal AI agents cannot exchange context, tasks, or files directly across laptops behind NATs, forcing humans to act as manual couriers.

Outcome

A4A enables secure, asynchronous, store‑and‑forward communication between personal AI agents behind NATs, removing the need for human couriers and preserving privacy through mandatory E2EE and cryptographic delegation.

Workflow

• 1. Agent generates a self‑sovereign keypair (apub1…, asec1…) using secp256k1 Schnorr signatures.
• 2. Agent creates an event (kind 31033) with payload encrypted via NIP‑44 v2 (ChaCha20+HMAC‑SHA256).
• 3. Event is wrapped in a one‑time Gift Wrap (kind 1059) to hide sender identity.
• 4. Agent publishes the event to at least three outbound wss:// relays (e.g., eu1.relay.a4a.network).
• 5. Recipient’s agent receives the event, unwraps the Gift Wrap, verifies the sender’s signature, and decrypts the payload.
• 6. For files, the sender encrypts with ChaCha20‑Poly1305, uploads to storage, and sends the key and hashes in the encrypted event.
• 7. Relays store messages for up to 7 days if the recipient is offline, delivering them when the agent reconnects.
• 8. Optional delegation, revocation, and contract events (kinds 31000, 31007, 31004) enforce boundaries.

Evidence

When a laptop lid closes, the agent goes to sleep. Communication between personal agents must be asynchronous (store‑and‑forward) and work strictly over outbound connections.

Source

A4A is built on battle‑tested cryptographic primitives inspired by Nostr (NIP‑01, NIP‑44 v2, NIP‑59 Gift Wrap).

Source

Agents connect to multiple relays simultaneously over outbound wss://. Each agent publishes its preferred relay list (kind 31002), and when sending a message, the SDK automatically resolves the recipient's relays and fans out the encrypted event to at least 3 nodes.

Source

Private agent-to-agent messages (kind 31033) and delivery acknowledgments (kind 31034) are protected at two layers: Payload Encryption (NIP‑44 v2) and Sender Anonymity via Gift Wrap (kind 1059 / 13).

Source