99 NIPs
Every NIP in one place. Search by meaning or keyword, filter by status, and open any NIP to edit the JSON it defines and see what each field does.
Keyword results are instant. When you start typing, a small search model loads on your device (once) to match by meaning too.
NIP-01 Draft Events
The core of Nostr: one signed JSON object called an event, and the handful of messages clients and relays exchange over a WebSocket to publish and subscribe to events.
NIP-02 Final Events
Kind 3 is your follow list: one p tag per person you follow, with an optional relay hint and a local nickname (petname). Publishing a new one replaces the old one.
NIP-03 Unrecommended Events
Kind 1040 carries an OpenTimestamps proof that an event existed by a certain Bitcoin block. Marked unrecommended upstream: vulnerable to one specific attack and awaiting an update.
NIP-04 Unrecommended Events
The original encrypted DM: kind 4 with AES-CBC content addressed to one p tag. Deprecated in favor of NIP-17 because it leaks who talks to whom and uses weak cryptography.
NIP-05 Final JSON document
Lets you show an email-like name such as alice@alpha.example: the domain serves /.well-known/nostr.json mapping names to public keys, and clients check that it matches.
NIP-06 Unrecommended Encoding
Derives Nostr keys from a BIP-39 seed phrase along the path m/44'/1237'/<account>'/0/0. Unrecommended upstream: prefer handling a single nsec.
NIP-07 Draft Behaviour
A browser extension exposes window.nostr so websites can get your public key, sign events and encrypt messages without ever seeing your secret key.
NIP-08 Unrecommended Events
The old way to mention people and notes: replace the mention with #[index] pointing into the tags array. Deprecated in favor of NIP-27 nostr: URIs.
NIP-09 Draft Events
Kind 5 asks relays and clients to delete your own earlier events, referenced by e or a tags. It is a request: nothing can guarantee deletion everywhere.
NIP-10 Draft Events
Kind 1 is the plain-text note. Marked e tags (root, reply) build threads, p tags notify everyone in the conversation, and q tags cite quoted events.
NIP-11 Draft JSON document
Relays describe themselves with a JSON document served over HTTP at their WebSocket URL: name, admin contact, supported NIPs, limits and fees.
NIP-12 Merged Behaviour
Deprecated: merged into NIP-01. It introduced filters on any single-letter tag, such as {"#t": ["nostr"]}.
NIP-13 Draft Events
Spend CPU to make an event id start with zero bits. A nonce tag records the counter and the committed target, so relays can demand a minimum difficulty against spam.
NIP-14 Draft Events
Adds a subject tag to kind 1 notes so clients can list threads by title, like email subjects.
NIP-15 Unrecommended Events
Stalls, products, auctions and NIP-04 checkout messages for decentralized shops. Unrecommended upstream as too complicated: use NIP-99 classified listings instead.
NIP-16 Merged Behaviour
Deprecated: merged into NIP-01. It introduced replaceable and ephemeral kind ranges that change how relays store events.
NIP-17 Draft Events
Private chats that hide who talks to whom: messages are unsigned rumors, sealed with NIP-44 by the sender and gift-wrapped with a throwaway key to each participant's DM relays.
NIP-18 Draft Events
Share someone else's event with your followers: kind 6 reposts a text note, kind 16 reposts anything else, and q tags turn a mention into a quote post.
NIP-19 Draft Encoding
Human-friendly strings like npub1…, nsec1… and nevent1… for showing and sharing keys, ids and pointers. Only for display and input: events and filters always use hex.
NIP-20 Merged Behaviour
Deprecated: now part of NIP-01. Defined the OK message a relay sends back after you publish an event, saying whether it was stored and, if not, why.
NIP-21 Draft Encoding
Put "nostr:" in front of a NIP-19 code (npub, nprofile, note, nevent, naddr) and you get a link any Nostr app can open, inside notes, on web pages or in QR codes.
NIP-22 Draft Events
Kind 1111 comments: a reply thread you can hang off anything, an article, a file, a podcast episode or a plain web URL, using upper-case tags for the root and lower-case tags for the parent.
NIP-23 Draft Events
Articles and blog posts as kind 30023: Markdown content plus title, summary, image and hashtag tags. Each article has a d tag, so you can edit it and links keep pointing at the latest version.
NIP-24 Draft Events
A catalogue of widely used extras that no other NIP owns: profile fields like display_name, website, banner, bot and birthday, plus the generic r, i, title and t tags.
NIP-25 Draft Events
Likes, dislikes and emoji reactions as kind 7 events that point at the note you reacted to. "+" is a like, "-" a dislike, anything else an emoji. Kind 17 does the same for web pages and other things outside Nostr.
NIP-26 Unrecommended Events
Unrecommended: use NIP-46 remote signing instead. Let one key publish on behalf of another through a signed delegation tag limited by kind and time window.
NIP-27 Draft Events
How to mention people and quote events inside a note's text: write nostr: links in the content, and add p or q tags when you want the person notified or the quote counted.
NIP-28 Unrecommended Events
Unrecommended: use NIP-29 relay-based groups instead. Open chat channels built from five kinds: create a channel (40), update its info (41), post messages (42), and hide messages (43) or mute users (44) for yourself.
NIP-29 Draft Events
Closed or open groups that a relay enforces: members post with an h tag, admins manage the group with kinds 9000–9020, and the relay publishes the group's metadata, admins and members as kinds 39000–39005.
NIP-30 Draft Events
Use your own images as emoji: write :shortcode: in the text and add an emoji tag that maps the shortcode to an image URL. Works in profiles, notes, comments, reactions and statuses.
NIP-31 Unrecommended Events
Unrecommended, though alt tags are still common. Give custom-kind events an alt tag with a one-line human description, so clients that don't know the kind can still show something sensible.
NIP-32 Draft Events
Attach labels to events, people, relays, URLs or topics with kind 1985: an L tag names the vocabulary, l tags carry the labels. Authors can also label their own events. Used for moderation, licences, languages and classification.
NIP-33 Merged Behaviour
Deprecated: renamed "addressable events" and moved into NIP-01. Kinds 30000–39999 are replaced per author and d tag, so the newest version wins and one address always finds it.
NIP-34 Draft Events
Code collaboration over Nostr: announce git repositories, publish their branch state, and send patches, pull requests, issues and status updates as events, with no central forge.
NIP-35 Draft Events
A searchable torrent index on Nostr: kind 2003 lists a torrent's info hash, files, trackers and catalogue ids (IMDb, TMDB…) so anyone can build the magnet link. No torrent files are stored on Nostr.
NIP-36 Draft Events
Add a content-warning tag, with an optional reason, and clients hide the event behind a "show anyway" button until the reader chooses to see it.
NIP-37 Draft Events
Save unfinished posts of any kind on relays without anyone else reading them: the draft is encrypted to yourself with NIP-44 inside a kind 31234 wrap, with optional checkpoints and a private relay list.
NIP-38 Draft Events
Share a live status next to your name, like what you're doing or the song you're playing, as a kind 30315 event that can expire on its own.
NIP-39 Draft Events
Prove you also own accounts elsewhere (GitHub, Mastodon, Bluesky, Telegram, Discord…): list them in a kind 10011 event, each pointing at a public post where that account names your npub.
NIP-40 Draft Events
Adds an expiration tag so an event can say when it stops being relevant. Supporting relays stop serving it after that moment and clients hide it, which suits temporary announcements and time-limited offers.
NIP-42 Draft Relay messages
Lets a relay ask "who are you?" before serving or accepting events. The relay sends a challenge, the client signs a short-lived kind 22242 event that echoes it, and the relay then knows which pubkey is on the other end of the connection.
NIP-43 Draft Events
Gives membership relays a shared vocabulary: the relay publishes who its members are and what roles exist, users ask to join with an invite code or ask to leave, and the relay announces each change as a signed event.
NIP-44 Draft Encoding
The encryption format Nostr uses today: two keys agree on a shared secret, the text is padded to hide its length, encrypted with ChaCha20, authenticated with HMAC-SHA256 and packed into one base64 string with a version byte. It defines no event kind; other NIPs put the result in an event's content.
NIP-45 Draft Relay messages
Adds a COUNT verb so a client can ask a relay "how many events match?" instead of downloading them all. Relays may return an approximate number and a HyperLogLog sketch that clients can merge across relays.
NIP-46 Draft Events
Keeps your secret key in one place, a "bunker", and lets apps ask it to sign. The app and the bunker talk through encrypted kind 24133 events on relays, using JSON-RPC-style requests such as sign_event, get_public_key and nip44_encrypt.
NIP-47 Draft Events
Lets an app pay and create Lightning invoices through your wallet without holding your funds. The wallet gives the app a connection URI; the app then sends encrypted requests such as pay_invoice over relays and gets encrypted results back.
NIP-48 Draft Events
Marks events that were copied into Nostr by a bridge from ActivityPub, Bluesky, RSS or the web. A proxy tag points back to the original object, so clients can link to it and avoid showing the same post twice.
NIP-49 Draft Encoding
Defines ncryptsec, a password-protected form of a secret key. The password is stretched with scrypt, the key is encrypted with XChaCha20-Poly1305, and the result is a bech32 string starting with ncryptsec1 that is safe to back up but not to publish.
NIP-50 Draft Relay messages
Adds a search field to REQ filters so clients can ask relays for full-text results, such as "best nostr apps". Relays rank results by relevance instead of date and may support extra key:value options like language:en.
NIP-51 Draft Events
A family of list events: one-per-user standard lists (mutes, pins, bookmarks, search relays…) and named sets you can have many of (follow sets, curation sets, relay sets…). Items go in tags when public, or in encrypted content when private.
NIP-52 Draft Events
Calendar entries as Nostr events: all-day events by date, timed events with time zones, calendars that group them, and RSVPs where people answer accepted, declined or tentative. Recurring events are deliberately left out.
NIP-53 Draft Events
Describes live streams and audio/video rooms as events that update while they run: who is hosting, where to watch, how many people are in. Viewers chat with kind 1311 messages, and listeners in a room signal their presence and raised hands.
NIP-54 Draft Events
An open encyclopedia where anyone can write an article on any topic. Articles are addressable kind 30818 events in Djot, many authors can cover the same topic, and readers choose versions through reactions, follows and trusted relays. Forks, merge requests and redirects are events too.
NIP-55 Draft Behaviour
Lets Android apps (and web pages opened on Android) ask a separate signer app to sign events and encrypt or decrypt messages, so only the signer ever holds the secret key. Requests go through intents, a background content resolver or nostrsigner: links.
NIP-56 Draft Events
A kind 1984 report flags a profile, a note or a media file as objectionable, with a type such as spam, impersonation or malware. Anyone can read reports; clients and relays decide for themselves whether to act on them, typically trusting reports from people you follow.
NIP-57 Draft Events
Zaps are Lightning tips recorded on Nostr. The sender signs a zap request and gives it to the recipient's Lightning wallet instead of publishing it; once the invoice is paid, the wallet publishes a zap receipt so everyone can see who zapped what.
NIP-58 Draft Events
Anyone can design a badge and award it to people. Awards are permanent and cannot be transferred, but each recipient chooses which badges to show on their profile and in what order, and can group them into sets.
NIP-59 Draft Events
Hides who is talking to whom by nesting an event in two encrypted envelopes. An unsigned rumor goes inside a seal signed by the real author, and the seal goes inside a gift wrap signed by a throwaway key, so relays only see a random sender and the recipient.
NIP-5A Draft Events
Host a static website on Nostr: a signed manifest maps each file path to the sha256 of a blob on Blossom servers, and a host server turns that into a normal website.
NIP-60 Draft Events
Keeps an ecash (Cashu) wallet on your relays, encrypted to yourself, so the same balance shows up in every app you sign in to.
NIP-61 Draft Events
Tips paid in Cashu ecash: the sender publishes ecash locked to the recipient's key, so the payment itself is the public receipt.
NIP-62 Draft Events
A signed request asking relays to permanently delete everything a key has published, either on named relays or everywhere at once.
NIP-64 Draft Events
Kind 64 notes carry chess games in PGN, the plain-text format chess software already reads, so clients can draw the board.
NIP-65 Draft Events
Your kind 10002 relay list says where you publish and where you read mentions, so others know where to find you (the outbox model).
NIP-66 Draft Events
Monitors probe relays and publish what they find (uptime, speed, supported NIPs, rules), so clients can discover relays and skip dead ones.
NIP-67 Draft Relay messages
Relays can add a hint to EOSE saying whether they sent every stored match or have more, so clients know when to stop paging.
NIP-68 Draft Events
Kind 20 posts are built around photos, Instagram-style: images hosted elsewhere and described in imeta tags, with a caption as content.
NIP-69 Draft Events
A shared format for bitcoin buy and sell offers, so P2P trading platforms can publish into one public order book instead of separate silos.
NIP-70 Draft Behaviour
Adding a ["-"] tag tells relays that only the author may publish this event, so others can't copy it to relays where it wasn't meant to be.
NIP-71 Draft Events
Dedicated video posts for YouTube- or TikTok-style clients: landscape (kind 21) or short vertical (kind 22), with every resolution and audio track listed in imeta tags.
NIP-72 Unrecommended Events
Reddit-style communities where moderators approve posts. Not recommended any more: new projects should use NIP-29 relay-based groups.
NIP-73 Draft Events
i and k tags point Nostr events at things outside Nostr (books, web pages, podcasts, places, blockchain transactions) so you can find every comment about them.
NIP-75 Draft Events
A fundraising goal as a kind 9041 event: a target amount and the relays where zaps are counted. Zap the goal to contribute and watch the progress bar fill.
NIP-77 Draft Relay messages
A way for a client and relay (or two relays) to find out which events each one is missing by exchanging compact fingerprints instead of full id lists.
NIP-78 Draft Events
Lets apps store their own private data, such as settings, on your relays in any format they like, as kind 30078 (one record per key) or kind 78 (many records).
NIP-7D Draft Events
Forum-style discussions: a kind 11 event with a title starts a thread, and every reply is a NIP-22 comment pointing at that thread.
NIP-84 Draft Events
Kind 9802 saves a passage you liked from an article, a web page or any other source, with a link back to where it came from and who wrote it.
NIP-85 Draft Events
Lets heavy calculations like web-of-trust scores or follower counts run on a service you choose, which publishes the results as signed events your client can simply read.
NIP-86 Draft HTTP
An HTTP API, on the same address as the relay's WebSocket, that lets a relay operator ban pubkeys, allow kinds and moderate events with simple JSON-RPC calls signed through NIP-98.
NIP-87 Draft Events
Ecash mints announce themselves with an event, and people recommend the mints they trust, so a wallet can find a mint through the people you follow.
NIP-88 Draft Events
A poll is a kind 1068 event with a question and options; each vote is a kind 1018 event sent to the relays the poll names, and clients count one vote per person.
NIP-89 Draft Events
When your app meets an event kind it can't show, it can find an app that can: apps announce which kinds they handle (31990) and people recommend them (31989).
NIP-90 Unrecommended Events
A marketplace for paid computation over nostr: you post a job (translate, summarize…), services compete to do it and post the result. Now unrecommended in favour of smaller, use-case-specific specs.
NIP-92 Draft Events
When a note links to an image or video, an imeta tag describes that file (type, size, dimensions, hash, alt text) so clients can show a good preview before downloading it.
NIP-94 Draft Events
Kind 1063 describes a shared file (where to download it, its type, hash, size and previews) so file-sharing apps can index and filter files on relays.
NIP-96 Unrecommended HTTP
A REST API for uploading files to storage servers with nostr auth, then linking them in notes. Now unrecommended: use Blossom (NIP-B7) for new apps.
NIP-98 Draft HTTP
Log in to an HTTP API with your nostr key: sign a short-lived kind 27235 event naming the exact URL and method, and send it in the Authorization header.
NIP-99 Draft Events
Kind 30402 is a classified ad: something for sale, rent or free, written in Markdown with a title, price, location and images, and editable because it's addressable.
NIP-A0 Draft Events
Short voice notes of up to about a minute: kind 1222 for a new message and kind 1244 for a voice reply, each pointing to an audio file.
NIP-A3 Draft Events
A kind 10133 list of the ways people can pay you, such as Bitcoin, Lightning or PayPal, each written as a payto tag with a type and an address.
NIP-A4 Draft Events
Kind 24 is a short public message addressed to one or more people, shown in their notifications rather than in feeds, with no threads and no privacy.
NIP-B0 Draft Events
Save and share web bookmarks as kind 39701 events: the d tag is the bookmarked URL, and you can edit the title, tags and notes later.
NIP-B7 Draft Events
Use Blossom servers for media: files are stored and found by their sha256 hash, and your kind 10063 server list tells others where to look when a link stops working.
NIP-BE Unrecommended Behaviour
Unrecommended. Two nearby devices sync Nostr events over Bluetooth Low Energy without internet: one acts as a relay, the other as a client, using NIP-77 to work out what is missing.
NIP-C0 Draft Events
Share code as kind 1337 events: the content is the code, and tags give the language, file name, license, dependencies and source repository.
NIP-C7 Draft Events
Kind 9 is a chat message. To reply, send another kind 9 that quotes the earlier message with a q tag, so chats stay a simple ordered stream.
NIP-CC Draft Events
Geocaching on Nostr: hide a cache as a kind 37516 listing, log finds as kind 7516, prove you were there with a kind 7517 event signed by the cache's own key, and group caches into trails.
NIP-EE Unrecommended Events
Unrecommended, superseded by the Marmot Protocol. Defined end-to-end encrypted direct and group chats on Nostr using MLS (RFC 9420), with forward secrecy and post-compromise security.
NIP-F4 Draft Events
Podcasts as Nostr feeds: each show has its own keypair, publishes kind 10154 show info and one kind 54 event per episode, and hosts confirm they author it with kind 10164.