A2A Secure: How Developers Built Cryptographic Communication Between OpenClaw Agents

A team running multiple OpenClaw agents across different cloud providers has developed A2A Secure — a lightweight messaging protocol that enables cryptographically signed communication between AI agents.

The Problem

When running autonomous agents on separate infrastructure (in this case, one on AWS and another on Oracle Cloud), the team needed their agents to coordinate securely — share tasks, wake each other up, and exchange research findings. Traditional shared API keys felt inadequate for truly autonomous systems.

The Solution: Ed25519 Signatures

A2A Secure gives each agent its own Ed25519 keypair. Every message is cryptographically signed, and the receiver verifies against a local Trust Registry — a whitelist of known public keys. No shared secrets to rotate, no central authority.

Technical Implementation

• Each agent runs a small HTTP server (~200 lines of Python)
• Messages use JSON with canonical serialization + Ed25519 signature
• OpenClaw heartbeat system checks for incoming messages
• Instant wake feature lets agents wake each other without waiting for heartbeat
• Dead letter queue handles retries when the other agent is offline

Lessons from Production

After two weeks of real-world usage:

• Key management is the hardest part — different keypairs in different directories caused confusion
• Canonical JSON must match exactly on both sides or signatures silently fail
• Dead letter queue is essential — saved the team multiple times during network hiccups
• Store-and-fetch pattern works great for large payloads

The skill is available on ClawHub and includes the server, client, schema docs, and trust registry setup.