Feature Request: Native Agent Notification Protocol (ANP) Core Plugin

[DIALLOUBE-RESEARCH]

TL;DR: Introduce decentralized, zero-config, anti-spam Push Notifications to ElizaOS agents using the open Web3 standard NattSquare Protocol (NSP).

---

🎯 Is your feature request related to a problem? Please describe.

I am building a Web3 Application Ecosystem where multiple distinct AI agents need to coordinate dynamically. Currently, agents operate in extreme isolation.

The Problem: Eliza agents lack a standard, permissionless way to announce state changes, trades, or lifecycle events to other agents asynchronously.

Approach	Drawbacks
Custom Webhooks	Demands prior knowledge of IP/endpoints, API keys, and immense integration overhead. Impossible to scale for dynamic discovery.
Message Brokers (Kafka)	Introduces a massive centralized single point of failure. Violates the permissionless, trustless nature of Web3 open networks.

This creates a massive bottleneck for cross-framework Agent-to-Agent (A2A) communication across the open web.

---

💡 Describe the solution you'd like

I would like elizaOS to natively support the NattSquare Protocol (NSP) by introducing a new core plugin: @elizaos/plugin-nsp.

NSP is an open, decentralized standard built specifically for A2A communication. The plugin would allow Eliza agents to broadcast decentralized, zero-config Push Notifications to other AI agents globally bypassing central infrastructure. The engine operates via:

• 🔒 Encrypted Full-Duplex WebSockets (wss://)
• 🛡️ Web3 ECDSA Wallet Signatures
• ⛏️ Hashcash Proof-of-Work (PoW) for network-edge Anti-Spam (0.1s latency)

Specifically, developers could equip their Eliza agents with this plugin to broadcast semantic intents (INFORM, REQUEST) and custom event payloads via standard actions. Other agents (Eliza, LangChain, AutoGPT) mathematically prove their identity using their wallet's private key and subscribe to the global event stream, enabling true decentralized multi-agent interoperability with a "Zero Backdoors" policy.

---

🏗️ Proposed Implementation

The nsp-plugin would introduce an Action (e.g., BROADCAST_NSP_NOTIFICATION) that agents can trigger to send events, and a Service to securely listen to events.

We have already shipped the V2 Military-Grade architecture and published the official TypeScript SDK (nsp-sdk-ts on NPM). The SDK automatically abstracts the WebSocket lifecycle, the Hashcash PoW mining, and the ECDSA cryptographic authentication natively.

import { Plugin } from "@elizaos/core";
// Import from the official NPM SDK
import { NSPBroadcastAction, NSPListenerService } from "nsp-sdk-ts";

// 1. Configure the Action to point to the Production Relay
const broadcastAction = new NSPBroadcastAction({
    relayUrl: "wss://nsp.hypernatt.com",
    authToken: "0x_ECDSA_Signature_or_API_Key" // Web3 Identity
});

// 2. Wrap it into an ElizaOS Plugin
export const nspPlugin: Plugin = {
    name: "nsp",
    description: "Broadcast decentralized Push Notifications to other AI Agents via the NattSquare Protocol (NSP)",
    actions: [
        broadcastAction // Sends intents with Hashcash PoW over secure WSS
    ],
    services: [
        new NSPListenerService("wss://nsp.hypernatt.com") // Listens to inbound events
    ]
};

---

🌍 Additional Context & Live Production

🚨 V2 Architecture is Live and Tested!
We have officially moved to Production V2 with a globally accessible Relay Node (wss://nsp.hypernatt.com), natively supporting Web3 Wallet Signatures for authentication.

• 📦 Official TypeScript SDK: Available on NPM (nsp-sdk-ts)
• 🛠️ Reference Implementation: DIALLOUBE-RESEARCH/nsp-protocol
• 🔥 Live Validation: We successfully routed traffic between autonomous LLMs responding to WebSocket intents using this exact production stack today.

With this integration, ElizaOS could lead the Web3 agent ecosystem by natively supporting permissionless, cross-framework Agent-to-Agent (A2A) communication right out of the box.

I am ready to submit a PR with full tests and documentation leveraging our newly published TypeScript SDK if this architectural direction is initially approved!

Author: Hamet Diallo — HyperNatt (DIALLOUBE-RESEARCH)
Contact: contact@hypernatt.com | hypernatt.com