All specifications

A timeline card is an addressable event placing one dated fact on a shared timeline. Cards carrying the same collection label form a collection; any key may...

Two additional NIP-46 methods, signeventcommit and signeventreveal, that let a client force a remote signer to commit to its BIP-340 signing nonce before the...

Groups whose membership and rules are enforced by the relay hosting them, identified by an id scoped to that relay.

This NIP defines a way for clients to authenticate to relays by signing an ephemeral event.

Kind 31436, numbered after RFC 1436, defines one text document at one absolute path. A collection of these addressable events under one pubkey can be presented...

Setup flow, implementation guide, key recovery, trust assumptions

Services describe themselves to their owner, so that an inventory of what someone runs is a side effect of running it rather than a list kept by hand.

Nostr Wallet Connect, where a client drives a remote Lightning wallet through encrypted events.

Kind 39701, a web bookmark addressed by its own URI, editable by whoever saved it.

Secrets derived from a seed phrase, so a wallet can regenerate its ecash after losing the device that held it.

Minting several quotes in one atomic request.

Code collaboration on Nostr: repository announcements, repository state, patches, and issues.

A marketplace protocol built from stalls, products and order messages, kept for the clients that implemented it.

A single addressable event kind for a private-by-default file/folder tree ("a drive"). Files and folders are the same kind of event; the node's type, name...

Defines a protocol for a private encrypted file drive using Blossom blob servers for file storage and Nostr relays for an encrypted file index.

An extension to NIP-58 for requestable badges, with private notifications for issuers.

Melting: the two-step flow where a wallet asks the mint to pay a request and spends ecash to cover it.

Minting: the two-step flow where a wallet requests a quote, pays it, and then asks the mint to issue ecash.

A bech32m encoding of payment requests, smaller than the CBOR form and friendlier to QR codes.

A request format carrying everything a sending wallet needs, so a transaction can be started by whoever is being paid.