Technical specifications, signed and public
Anyone can publish a protocol, a format or a convention here. Each document is a Nostr event signed by its author and stored on relays: this site renders and indexes them, it does not own them.
Or write a document of your own.
Recently published
Browse all
Place Photos and Videos
This NIP defines a standardized event format for sharing photos and videos tied to specific real-world locations (e.g., OpenStreetMap POIs). Each event carries...
reviewcovers360Place Photos and Videos
Maven Repositories
This NIP defines how to publish Maven artifacts (jars, aars, klibs, POMs, Gradle module metadata, sources, javadoc, signatures) as [Blossom][] blobs pinned by...
reviewcovers3071library release
Scheduled Tasks
A user's recurring jobs (a daily front page, a weekly digest), shared by every client they sign into. Any of their devices may run a task; the first to claim...
reviewcovers34817Scheduled Tasks
AI Agent Keys
A user stores the API key of their AI provider so every client they sign into can run AI tasks for them, billed to the user.
reviewcovers12000AI Agent Keys
NIP-XX: WebRTC Sessions
This NIP defines an addressable event that announces a live, joinable session (a multiplayer game, a collaborative music jam, a shared whiteboard, a co-editing...
covers35050session2050invite
NoorNote
NoorNote is a privacy-first Nostr client for desktop (macOS/Linux), Android and web. This is its public capability profile: the Nostr event kinds it can create and/or render. Directories and other clients can read the k-tags below to discover that NoorNote supports a given kind.
covers0Profile Metadata1Short Text Note3Follow List4Encrypted DM (legacy)5Event Deletion6Repost+67 more
NIP-MDM
NIP-MDM (Masked Direct Messages): one-to-one DMs that hide the sender. The sender writes under a per-recipient NIP-SKD “masked key” so its root never appears on the wire, while the recipient is addressed by their real key and can still cryptographically verify who sent it. Accountable sender pseudonymity, stable, verifiable, orderable and bannable identities and editable messages, over ordinary kind-10002 relays, with no new signer ops beyond NIP-SKD.
3495d9covers30092Masked Direct Message#dm#chat#direct-messaging
Mind Maps
A mind map is a tree of short ideas around one central topic. This spec stores one as an addressable event, so it can be shared, edited by its author, forked...
covers30627Mind Map
NIP-SKD
NIP-SKD adds two signer capabilities: deriving app-scoped sub-keys from a user’s identity key in three forms (self, shared, and blinded), and operating as those sub-keys without ever exposing their private material to the client. The result is a private, deterministic keyspace of per-context identities, reproducible on any device holding the root key, unlinkable in public, and usable through remote or browser signers.
893519#signers
NIP-LRS
A desktop Nostr signer exposes its NIP-46 interface over a **private relay bound to localhost**, so any NIP-46-capable client on the same machine — a web app in the browser, or an installed app — can sign through it with **no relays and no key material leaving the signer**, and — on the one-click discovery path — **no pairing string**.
7f00b1#signer
Napplet Handler Preferences
This NIP defines an addressable event that records which napplets a user prefers to handle an archetype's intents. Shells use it to sync preferred handler...

Generic Lists
NIP-51 assigns a new event kind to every list. A kind requires a merged NIP to be assigned, and any draft using an unassigned one can be overwritten by a later...
covers36205Generic Lists#nip#nostr
NIP: Computed Home Relays
Find anyone's NIP-65 relay list from their pubkey alone, on relays every client computes the same way.
covers10002Relay List Metadata#nostr#nip#dht#relays
BUD: Inbox servers
Lets a user list the Blossom servers that receive the blobs other pubkeys send them, with their user server list as fallback.
draftcovers11708Inbox server list#bud#blossom
BUD: Blob pinning
Lets a client ask a Blossom server to keep a blob for itself or for other pubkeys, pin an already stored blob by its hash, and check its own pin.
draftcovers24242Blossom authorization#bud#blossom
NIP-SHORT
NIP-SHORT defines short, compact references for Nostr events. Instead of sharing a long `nevent1…`, `naddr1…`, or `note1…`, the author embeds a compact code **directly inside the event** as a single-letter tag. A client resolves a short address to its event with a single relay query and verifies it locally.
03f210#short
NIP-XX: Bitcoin-OTC Identity Linkage Proof
Final/awaiting number assignment
covers37773Bitcoin-OTC Identity Linkage Proof
Citations
This NIP defines the basic structure of citations required for embedded quotes, footnotes, endnotes, in-line references, appendices, and prompt records. It covers internal (to Nostr addresses) and external (to the wider web or printed material) citations.
covers30internal reference31external web reference32hardcopy reference33prompt reference#citations#quotes#appendix
Highlights
This NIP defines kind:9802, a "highlight" event, to signal content a user finds valuable by quoting and marking it.

[NIP-5D] Nostr Web Applets (napplets)
This NIP defines a web projection for sandboxed web applications ("napplets") running in iframes to communicate with a hosting application ("shell"). Shells...
reviewcovers5129napplet snapshot15129root napplet35129named napplet
Directories
Nostr-based directory system
#directory#unix#filesystem
NIP-CD: Slash Commands
Slash commands: kind 31992 defines one, and invoking it is plain text at the start of any event's content, so no client has to support it.
draftcovers10992Installed slash commands31992Slash command definition#nostr#nip
NIP-51: Lists
The list kinds, with public entries in the tags and private ones encrypted in the content: mutes, bookmarks, relay sets, follow sets and the rest.
draftcovers10000Mute list10001Pin list10002Relay List Metadata10003Bookmark list10004Communities list10005Public chats list+27 more#nostr#nip
NIP-54
This NIP defines kind:30818 (an addressable event) for descriptions (or encyclopedia entries) of particular subjects, and it's expected that multiple people...

NUT-00: Notation, Utilization, and Terminology
The notation, models and cryptography the rest of the specification is written in: blinding, signing, proofs, and how a token is serialised.
mandatory#cashu#ecash#nut
NIP-A3: payto: Payment Targets
Kind 10133, a list of payto tags saying where a key can be paid, on Bitcoin, Lightning or any other network.
draftcovers10133Payment Targets#nostr#nip
NUT-30: Payment Method: Onchain
Minting and melting with onchain Bitcoin payments.
optional#cashu#ecash#nut
NUT-29: Batched Minting
Minting several quotes in one atomic request.
optional#cashu#ecash#nut
NUT-27: Nostr Mint Backup
How a wallet backs up its mint list to Nostr relays, encrypted under keys derived from its own seed phrase.
optionalcovers30078Application-specific data#cashu#ecash#nut
NUT-26: Payment Request Bech32m Encoding
A bech32m encoding of payment requests, smaller than the CBOR form and friendlier to QR codes.
optional#cashu#ecash#nut