$ cat reference/nips.log
This relay implements a curated set of Nostr Implementation Possibilities (NIPs). Use this page as a quick memory aid and follow the spec links for full details straight from the source repo.
All summaries paraphrase the official markdown files maintained at github.com/nostr-protocol/nips.
Defines the canonical event envelope, message types, tags, and subscription flow that every Nostr client and relay speaks.
Introduces kind 5 deletion requests that reference prior events via e/a/k tags so relays and clients can hide or drop disowned content.
Specifies the HTTP metadata document (Accept: application/nostr+json) that advertises relay capabilities, policies, fees, and limits.
Defines the encrypted chat scheme that uses NIP-44 encryption plus NIP-59 gift wraps for kind 14/15 messages and DM relay hints.
Describes kind 30023/30024 Markdown articles with d-tag identifiers, metadata tags (title/image/summary), and NIP-22 comment threading.
Defines addressable events (kinds 30000-39999) that can be replaced by the same author using pubkey+kind+d-tag as the unique identifier. Supports Kind 30404 for NostrFeedz news subscriptions.
Adds the expiration tag so authors can set a unix timestamp where relays drop or stop serving the event and clients ignore it.
Defines AUTH messages and kind 22242 challenge events so relays can gate reads and writes behind signed, time-bound proofs.
Adds the search filter field so relays can interpret free-text queries, score results, and expose optional extensions like domain: or language:.
Introduces standard lists and addressable sets (follows, mutes, bookmarks, relay groups) with optional encrypted content so users can curate both public and private references.
Introduces kind 1984 reporting events with typed reasons (spam, malware, nudity, etc.) referencing pubkeys/events/blobs for moderation tooling.
Specifies kind 62 requests directing tagged relays (or ALL_RELAYS) to purge every event from a pubkey and block rebroadcasts going forward.
Defines kind 10002 events where users publish their preferred read/write relays, allowing clients to discover where to find them.
Relays publish kind 30166 events containing their own metrics, software version, and supported NIPs for decentralized monitoring.
Wraps the Negentropy range-based reconciliation protocol in NEG-* messages so clients and relays can sync event IDs efficiently.
Outlines an optional JSON-RPC management API (ban/allow keys, edit metadata, configure limits) authenticated with NIP-98 payloads.
Defines a standard for discovering content and curating collections of events, pubkeys, and other data to improve content discovery.