Hi Gnosis community, I’m GhostAgent the lead at GhostAgent.ninja. We’ve been heads-down building a stack that unifies Genome (.GNO), Safe (v1.4.1), and ERC-6551 to give agents a “Mirror Body”—a single 0x identity across Gnosis and Story Protocol.
The project developed through our efforts to create an MVP NFT “owned” email account. NFTmail.box.
We recently demoed this at the SURGE x Moltbook LABLAB hackathon, but as we move toward a production launch, we have some design choices regarding agent communications that affects the whole ecosystem.
The Current Setup: The “Mailbox Dependency”
Right now, our A2A (Agent-to-Agent) instructions and human-to-agent OTPs run through NFTmail.box, which currently uses Zoho Mail for its reliability and infrastructure. While ZOHO offers reliability and is privacy-centric,and it works great for a prototype, it leaves a “centralised shadow”:
- Platform Risk: The agent’s “inbox” depends on a Web2 provider’s uptime and TOS.
- The Encryption Gap: There is a momentary instance of cleartext during the relay process before it reaches the agent’s brain.
Our ambition is to build a truly sovereign, panopticon-proof tool on Gnosis, we are striving to decouple this communication layer from Web2 and move it to a decentralised transport
.
The Proposal: The GhostAgent Sovereign Bridge
We are seeking support/funding to develop a Sovereign A2A Bridge as a Gnosis public good. This would allow any .GNO-based agent to receive instructions via a decentralized network, keeping the entire lifecycle on-chain and encrypted.
The Technical Debate: XMTP vs. Waku
We are currently evaluating the transport layer for this bridge and would love input from the Gnosis Safe and Core teams:
- Option A: XMTP. Pragmatic, high deliverability, and has native E2EE via the MLS protocol. It handles offline message storage well, which is vital for autonomous agents.
- Option B: Waku. Deeply aligned with Gnosis’s history and privacy-first ethos. It offers better metadata protection but requires more infrastructure (Store nodes) to ensure agents don’t miss messages.
Our goal is to build a standard where the Safe is the inbox, and the .GNO domain is the identity.
