Great read! Prompted me to update the way I was signed in... 🥸

Great work! Really well put together... I think the only missing part is the marketing... I only came across it by accident when doom scrolling - and didn't see it on places like nostrapps.com or zapstore.dev? Also think you need to tell the creators what is better about it (for them) - zaps? decentralised? Whatever.. Maybe look for content creators using Peertube - offer to help repost their content or something... people like or

Published new Nostr Community Convention: ncc-06 - NCC-02 / NCC-05 Service Profile NCC-06 updated: NCC-02 / NCC-05 Service Profile NCC-06 now formally defines a service participation profile that composes NCC-02 and NCC-05 for identity-first, DNS-optional service discovery. It specifies what a service, sidecar, and client must do to support: Pubkey-owned service identity Deterministic client-side resolution and trust Dynamic endpoint rotation Tor and onion services as first-class endpoints Robust behaviour under partial failure and inconsistent data NCC-06 does not change underlying protocols, add new message types, or move resolution or trust logic into services. Services remain protocol-dumb. Clients remain in control. #nostr #ncc-02 #ncc-05 #ncc-06 #service #no-dns #nostrdev

Published new Nostr Community Convention: ncc-05 - Identity-Bound Service Locator Resolution NCC-05 update published NCC-05 now clearly defines identity-bound, encrypted service locator resolution for dynamic ip:port endpoints, without DNS or public infrastructure. What’s new and clarified: Explicit anchored vs unanchored operating modes Anchored mode (recommended): NCC-02 provides identity and trust, NCC-05 provides private reachability Unanchored mode (permitted): supports ephemeral, P2P, and bootstrap use cases Formalised endpoint object format with deterministic selection Stronger guidance on TLS key binding (k) to prevent endpoint substitution Clear TTL, expiration, caching, and refresh semantics Deterministic record and endpoint selection to improve interoperability Explicit support for private and invite-only services NCC-05 remains client-agnostic, relay-agnostic, and fully compatible with existing Nostr primitives, while enabling private, low-cost alternatives to Dynamic DNS. #nostr #nameresolution #privacy

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

NCC functional libraries now live on npm 🥳🥂🙌 These are the first functional JavaScript libraries for NCC-02, NCC-05, and NCC-06 are now published on npm and ready for people to give me shit about.... (😭) - ncc-02-js: Create, publish, and resolve NCC-02 service records. This standardises how a Nostr service describes itself and how clients discover it. - ncc-05-js: Handle encrypted endpoint records. This enables private and censorship-resistant service addressing without relying on DNS. - ncc-06-js: Sidecar tooling for managing, publishing, and rotating NCC-02 and NCC-05 records independently of relay core code. These libraries are deliberately small, explicit, and focused on correctness so they can be dropped into relays, sidecars, or client tooling without ceremony. npm: https://www.npmjs.com/package/ncc-02-js https://www.npmjs.com/package/ncc-05-js https://www.npmjs.com/package/ncc-06-js #nostr #ncc #npm #javascript #decentralisation #privacy #censorshipresistance #opensource #nostrdev

I got a working (tests and toys) version of discovery, authority and resolution using nostr itself ... removes the need for dns and CA.... I think it might help go part of the way https://github.com/imattau/ncc-06

An example #PoC is on #Github -> https://github.com/imattau/ncc-06... Passing most(!) tests.... atm Service Discovery and reachability - using #Nostr -

Interesting read if your into #nostrdev

💯 agree... I've found another good way is to use multiple AI - as the quite often have different perspectives and approaches. I've found when 1 gets stuck - pass it over to the next one to take a look. More often than not - it can fix the problem (seems even AI can get stuck in its own head..?) You can also add in the general GPT to help you explain your thoughts to the coding AI - without wasting development tokens.. 😊

Openhands is an option.... https://github.com/OpenHands/OpenHands

What NCCs are not: They are not authoritative and they do not reserve anything globally. Interesting fact: two conflicting NCCs can exist at the same time without protocol impact. #nostr #decentralisation #ncc #nostrdevs #nostrdev https://github.com/imattau/nostr-community-conventions