NIP-01
Basic Protocol Flow
The foundational specification defining how Nostr works: events, clients, relays, and basic protocol operations.
final core protocol
Author: fiatjaf
NIPs Reference
Nostr Implementation Possibilities — the technical specifications that define how Nostr works. From basic protocol operations to advanced features.
20
Total NIPs
10
Final
10
Draft
Filter by Category
Filter by Status
NIP-02
Contact Lists and Petnames
Defines how Nostr users maintain their following lists, organize contacts with custom names, and manage their social graph.
final social features
Author: fiatjaf, arcbtc
NIP-04
Encrypted Direct Messages
Defines how Nostr users send private, encrypted direct messages using kind 4 events and ECDH encryption.
final social features
Author: fiatjaf
NIP-05
DNS-based Verification (NIP-05 Identifiers)
Mapping Nostr public keys to human-readable internet identifiers using DNS and HTTPS, enabling verified usernames like alice@example.com.
final identity
Author: fiatjaf, mikedilger
NIP-07
window.nostr capability for web browsers
Defines window.nostr API for browser extensions to provide signing capabilities to web applications without exposing private keys.
draft application
Author: fiatjaf
NIP-09
Event Deletion
Defines how users can request deletion of their previously published events using kind 5 deletion events.
final content management
Author: fiatjaf
NIP-10
Reply Conventions (e and p tags)
Defines conventions for using e and p tags in replies to create threaded conversations and proper mention attribution.
final social features
Author: fiatjaf, arcbtc
NIP-13
Proof of Work
Defines proof-of-work system for Nostr events, requiring computational effort to combat spam and abuse.
draft relay features
Author: jb55, cameri
NIP-19
bech32-encoded Entities
Defines human-friendly bech32 encoding for Nostr entities (public keys, event IDs, etc.) using prefixes like npub, nsec, note, and nevent.
final data encoding
Author: jb55, fiatjaf
NIP-21
nostr: URI scheme
Defines nostr: URI scheme for creating universal links to Nostr profiles, notes, and other entities across clients and platforms.
draft application
Author: fiatjaf
NIP-23
Long-form Content
Defines how to publish long-form content like articles and blog posts on Nostr using parameterized replaceable events.
draft application
Author: fiatjaf
NIP-25
Reactions
Defines how users express reactions (likes, emoji responses) to events using kind 7 reaction events.
final social features
Author: fiatjaf
NIP-27
Text Note References
Defines how to embed nostr: references inline in text content, enabling rich mentions and content previews within notes.
draft application
Author: arthurfranca, mikedilger
NIP-28
Public Chat (Channel Events)
Defines public chat channels using kind 40 (channel creation), kind 41 (channel metadata), and kind 42 (channel messages).
final chat
Author: fiatjaf
NIP-33
Parameterized Replaceable Events
Defines parameterized replaceable events (kinds 30000-39999) with unique identifiers, enabling updatable content with stable addresses.
draft core protocol
Author: Semisol, fiatjaf
NIP-42
Authentication of clients to relays
Defines challenge-response authentication mechanism allowing relays to verify client identity before granting access.
draft relay features
Author: fiatjaf, Kukks, arthurfranca
NIP-50
Search Capability
Defines how relays can provide search functionality by supporting 'search' filter parameter for full-text and keyword searches.
draft relay features
Author: fiatjaf, mikedilger, monlovesmango
NIP-51
Lists
Defines how users can create and manage categorized lists for bookmarks, mutes, pins, and other collections on Nostr.
draft application
Author: fiatjaf, arcbtc, mikedilger, arthurfranca
NIP-57
Lightning Zaps
Defines how to send Bitcoin Lightning payments (zaps) to Nostr events and users, integrating value-for-value payments directly into the protocol.
final monetization
Author: jb55, kieran
NIP-65
Relay List Metadata
Defines how users specify their preferred relays for reading and writing events, enabling better content discovery and delivery.
draft relay features
Author: mikedilger, vitorpamplona
Understanding NIPs
What are NIPs?
Nostr Implementation Possibilities are the technical specifications that define how the Nostr protocol works. Think of them as building blocks—each NIP adds a specific feature or capability.
Why they matter
NIPs ensure interoperability. When clients implement the same NIPs, they can communicate seamlessly. You can post in Damus and see it in Primal because both follow NIP-01.
Categories
NIPs cover everything from core protocol (events, relays) to social features (DMs, reactions) to advanced use cases (marketplaces, media).
Status levels
Final = stable and widely implemented. Draft = in development, may change. Deprecated = replaced by better alternatives.
Essential NIPs
New to Nostr? Start with these fundamental specifications.
NIP-01: Basic Protocol Flow
The foundation of Nostr. Defines events, clients, relays, and basic operations. Start here if you're learning how Nostr works.
NIP-05: DNS-based Verification
Human-readable identifiers like alice@example.com. Essential for discoverability and identity verification.
NIP-19: bech32-encoded Entities
User-friendly formats like npub and note. Makes sharing public keys and event IDs easy.