You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(nip86): implement WebSocket relay management API #717
Currently, Nostream operators must manage the relay either via SSH or the built-in HTTP Admin Console. However, standard Nostr admin clients cannot interact with Nostream natively over WebSockets, breaking interoperability for operators who want to use generic ecosystem tools.
Proposed Solution
Implement NIP-86 to support standardized WebSocket RPC commands for relay administration.
Scope
Auth: Verify incoming ["admin", ...] messages against the configured relay operator's pubkey.
Commands: Implement handlers for core commands such as banning pubkeys, unbanning, deleting events, and querying relay status.
Database Integration: Connect the NIP-86 command handlers directly to the existing database repository functions being built for the HTTP Admin Console.
A new surface, not parity: the rewrite reproduces the capture's behaviour, and the capture has no NIP-86. The issue's own scope confirms it — ["admin", ...] RPC handlers wired to "the existing database repository functions being built for the HTTP Admin Console" — i.e. it was proposed on top of the TypeScript console that the rewrite is replacing, so its database-integration premise does not survive the port.
The rewrite's admin surface is #867: HTTP routes making the existing console work unmodified, plus an MCP server for agent-driven administration. NIP-86's command set overlaps the MCP tool set (relay_status, delete_event, user_admin, reports_*) almost exactly, so the honest post-cutover question is whether NIP-86 becomes a wire transport for tools #867 already builds — not whether it is ported.
Left without a milestone (out of the rewrite set), and recorded in the "Deferred past cutover" section of estimates.md.
Activity
chappie-daemon commentedon Oct 24, 2026
Decision (2026-10-24): post-cutover
A new surface, not parity: the rewrite reproduces the capture's behaviour, and the capture has no NIP-86. The issue's own scope confirms it —
["admin", ...]RPC handlers wired to "the existing database repository functions being built for the HTTP Admin Console" — i.e. it was proposed on top of the TypeScript console that the rewrite is replacing, so its database-integration premise does not survive the port.The rewrite's admin surface is #867: HTTP routes making the existing console work unmodified, plus an MCP server for agent-driven administration. NIP-86's command set overlaps the MCP tool set (
relay_status,delete_event,user_admin,reports_*) almost exactly, so the honest post-cutover question is whether NIP-86 becomes a wire transport for tools #867 already builds — not whether it is ported.Left without a milestone (out of the rewrite set), and recorded in the "Deferred past cutover" section of
estimates.md.