All specifications

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 NIP standardizes a deterministic method for deriving avatar from a user's pubkey. This ensures consistent visual identity across all Nostr clients.

How a server charges for an endpoint: a 402 response carrying the payment terms, for uploads, downloads or media processing.

Defines HEAD /upload, a preflight request telling a client whether an upload would be accepted before it sends the bytes.

Defines PUT /upload and the blob descriptor, the JSON object describing a stored blob: its url, hash, size, mime type and upload time.

When a user has no name or display_name in their kind 0 metadata, clients SHOULD display:

The base every Blossom server implements: the CORS headers, the error reporting, and the GET and HEAD endpoints that serve a blob by its hash.

Defines PUT /media, where a server transcodes and optimises what it is given rather than storing the bytes untouched.

Authors: decented

Defines PUT /mirror, which asks a server to fetch a blob from a URL itself instead of having the client upload the same bytes twice.

This NIP defines a standard HTTP API for relays to expose trust-weighted influence scores computed using the GrapeVine algorithm. These scores enable clients...

Defines the management endpoints: listing what a pubkey uploaded, and deleting a blob by its hash.