NCC-05: The Missing Layer for Peer-to-Peer Applications
Today, we successfully demonstrated the power of NCC-05 (Identity-Bound Service Locator Resolution) by building a functional reference implementation: NCC-P2P-CLI .
I'm a tech enthusiast exploring the intersection of Nostr, AI, privacy, and crypto - and now vibe-coding..
Big on Linux, obsessed with open systems...
In my downtime, I’m into photography, music making, and riding motorcycles — anything that gets me thinking or moving.
Today, we successfully demonstrated the power of NCC-05 (Identity-Bound Service Locator Resolution) by building a functional reference implementation: NCC-P2P-CLI .
Many networked systems assume that services must be named in order to be reachable. That assumption quietly binds identity, trust, and location together, making services brittle when they move, change networks, or need to limit who can find them. An alternative approach is to treat services as identities first and locations as optional, temporary attributes. From this framing, services can publish signed statements describing how they may be reached, while clients resolve those statements as data rather than through a naming hierarchy. Identity remains stable even as endpoints change or disappear. The result is infrastructure that tolerates mobility, partial availability, and privacy requirements without relying on DNS or other centralised resolution systems.
NCC-06 exists to address this problem directly. It defines an identity-first relay participation profile that allows relays to be discovered, resolved, and connected to using signed Nostr data, without relying on DNS or central registries.
NCCs are lightweight, Nostr-native conventions for client and ecosystem behaviour. Not protocol rules, not enforced standards. Just documented patterns that emerge, get copied, and evolve.
A lightweight, Nostr-native convention for mirroring RSS or Atom feeds with provenance, deduplication, and update handling.
Exploring a small, Nostr-native way for apps to discover and verify pubkey-owned services. Instead of relying on DNS and public CAs, this approach uses signed service records, key pinning, and optional third-party attestations to let Nostr apps securely connect to user-run backends. It is intentionally narrow, experimental, and aimed at builders rather than end users.
This document proposes a new Nostr event kind representing **protocol-level proposals**. These events are used to publish, revise, and reference proposals for Nostr conventions, new kinds, or other protocol behaviours directly on Nostr itself.
Nostr can act as an open, permissionless layer for sharing ideas, theories, and early research. It does not replace journals or peer review, but removes many of the barriers that stop ideas from being shared early. By allowing anyone to publish under a persistent identity, show revision history, and invite open critique, Nostr makes it easier for independent and interdisciplinary work to be seen, discussed, and improved in public.
ProtonMail’s encrypted email and Nostr’s decentralized network create a powerful duo for secure, private communication, protecting users from surveillance, censorship, and corporate data collection.
Nostr, a decentralized social media protocol, and the Lightning Network, a fast Bitcoin payment system, are transforming the internet. Together, they enable censorship-resistant interactions and direct, low-cost transactions, empowering users and creators. This combo offers a more open, fair, and resilient online experience, proving the decentralized web is the future. If you're using Nostr, adding Lightning unlocks even more possibilities.