All specifications

The core protocol: the event object, how its id and signature are computed, what makes a kind regular, replaceable or addressable, and the messages clients and relays exchange.

Kind 37516 and its companions, geocache listings and the logs of the people who found them.

Locking ecash to a public key, redeemable only against a Schnorr signature from the key that owns it.

Groups one or more Scheduler DVM jobs into a single scheduled item, and stores private context needed to display it later.

This document defines a portable, private address book.

A JSON-RPC WebSocket protocol for subscribing to quote and proof state changes instead of polling for them.

Blank outputs, which let a mint return the Lightning fees a wallet overpaid when melting.

This NIP defines a regular event kind that attests to a content-addressed archive of a Nostr identity's events and referenced media. The attestation is a...

A third element on EOSE, telling a client whether the relay really sent every stored event matching the filter.

36787: Music Track (addressable)

How a client on Android asks a signer application on the same device to sign, so it never handles the private key.

The imeta tag, which describes a media URL found in the content: its dimensions, its mime type, its hash and its fallbacks.

How an ecash mint announces itself and its capabilities, and how users recommend the mints they trust.

Gift wraps: a rumor sealed to its recipient, then wrapped again under a throwaway key, so relays see only the wrapper.

ncryptsec, a private key encrypted under a password, with scrypt deciding how expensive guessing it is.

This NIP defines event kinds for geocaching on Nostr. These events allow users to create, share, and log geocaches in a decentralized manner.

This spec defines an addressable event kind for publishing music playlists on Nostr. Tracks can be referenced either by Nostr-native coordinates (a tags) or by...

How two devices speak Nostr over Bluetooth Low Energy, emulating the websocket protocol within its limits.

The alt tag, a plain text summary so a client that does not know a kind can still show something for it.

The delegation tag, which let one key authorise another to sign events on its behalf.