All specifications

This NIP defines a way to generate and interpret Proof of Work for nostr notes. Proof of Work (PoW) is a way to add a proof of computational work to a note...

This NIP defines a standard for converting Bitcoin into smiles, a unit of joy emitted by humans upon receipt of value over Nostr. It deprecates NIP-57...

This NIP defines a committee management system for Nostr, enabling communities to create organizational structures with members, roles, and open positions...

This NIP defines kind:10133 for payment target events. This kind is replaceable.

This NIP defines how a Nostr user advertises a Bitcoin BIP-352 silent payment address, so that anyone can pay them on-chain without interaction, address reuse...

This document defines how to send and receive BIP-352 silent payments using a Nostr public key (npub) as the sole identity input. Every Nostr keypair...

Kind 31234, an encrypted draft of an unsigned event of any kind, stored on relays for its author alone.

Kind 30023, long-form articles written in Markdown, addressable so their author can revise them in place.

This has been vibed into existence and should be considered a joke until you realize it's not. I did not read this before publishing.

This NIP defines lists of things that users can create and that anyone can add to. It provides an alternative to NIP-51 for list management. The distinction is...

This specification defines three event kinds that represent collections of users: the Follow List (kind 3), the Mute List (kind 10000), and the People List...

These rules apply to both client and relay implementations.

A client connects to a relay using the WebSocket protocol. A relay accepts connections and upgrades HTTP requests to WebSocket.

A relay declaration is a signed Nostr event through which a user announces which relays they write their content to and which relays they monitor for content...

A Nostr relay may expose a machine-readable JSON document over HTTP that describes its identity, operator, capabilities, and operational constraints. Clients...

An event is the fundamental data unit. Every event contains exactly seven fields.

A standard for deriving deterministic, readable colors from Nostr pubkeys. This ensures consistent visual identity across all clients.

This NIP defines a decentralized monster-taming game protocol on Nostr. "Nostrmon" (Nostr Monsters) is a framework inspired by games like Pokémon, where...

This document defines the protocol for storing and synchronizing user settings across devices in Nostr Mail using NIP-78 application-specific data.

This NIP standardizes a deterministic method for deriving avatar from a user's pubkey. This ensures consistent visual identity across all Nostr clients.