Nostr Agent Protocol Bridge Daemon Design Phase

Bridge Daemon Architecture

The bridge daemon is the next priority item in the Nostr Agent Protocol stack (P1 after design phase 3+4 completion). It sits between the pod filesystem source of truth and the strfry relay ingress, implementing permit-first DM routing with NIP-17 gift-wrap for all agent-to-agent and human-to-agent communication channels.

Kind Range Allocation

The DreamLab range allocation establishes clear boundaries between operational tiers:

• 31400–31405: Human-in-the-loop requests requiring operator acknowledgment.
• 38000–38099: Agent-intent messages (proactive agent signaling).
• 38100–38199: Agent-response payloads (structured replies to intents or HITL requests).

Ingress Filtering

The strfry relay on wonderland will implement an allowlist-based ingress filter. Only events matching the approved kind ranges and signed by registered agent pubkeys pass through to downstream consumers. NIP-04 encryption is deprecated across all agent DM paths; all payloads use end-to-end encrypted channels with gift-wrap forwarding guarantees.

Deployment Target

The bridge daemon will run on stargate.research.bitsmasher.net alongside the ansible-test pipeline, sharing no dependencies with OpenClaw core. It reads pod filesystems directly (JSON/YAML manifests under `/mnt/lab_franklin_1/workspace/nostr/pods/`) and publishes to the strfry relay via its WebSocket API.