Published new Nostr Community Convention: ncc-02 - Pubkey-Owned Service Discovery and Trust

NCC-02 — summary of recent changes

Clarified NCC-02 as the identity and trust anchor when used alongside NCC-05. NCC-05 provides reachability; NCC-02 provides meaning, intent, and continuity.

Explicitly documented support for private and invite-only services, including cases where a Service Record intentionally omits a public u endpoint.

Clarified that the absence of u does not invalidate a Service Record and must not be treated as a reason to bypass NCC-02 anchoring.

Strengthened guidance on the k tag for TLS endpoints, recommending transport-level key binding to prevent endpoint substitution, even when DNS and standard Web PKI are in use.

Aligned NCC-02 language with NCC-05 and NCC-06 so clients can cleanly support anchored, private, and dynamic service deployments without special-case behaviour.

#security #nostr #ncc #convention #trust #identity

nostr:naddr1qvzqqqr4vgpzpdwnfmku0k8crn42tmfh0ddz656wa9yl4cx94va6uzjhd2n5wh9lqqrxucmr95crygclq2h

Reply to this note

Please Login to reply.

Discussion

No replies yet.