All specifications

This NIP defines event kinds to host asset prices.

A bulletin board is a relay-centric system of forums where users can post and reply to others, typically around a specific community. The relay operator...

Upon connection, and at any point during the connection, the Relay can send a FEATURES payload reflecting the available commands to the client and its user.

Use kind 255 to create events for testing purposes only, such as inside of automated tests in your application.

Defines PUT /report, where a client submits a signed NIP-56 report naming the blobs it objects to.

Defines kind 10063, the replaceable event where a user lists the Blossom servers holding their blobs, most trusted first.

How a Nostr client uses Blossom for media: reading a user's server list, and uploading to the servers it names.

Paying one Lightning invoice from several mints at once, all of them or none.

How a server returns NIP-94 file metadata alongside a blob descriptor, so a client can publish the file without recomputing it.

The window.nostr object a browser extension exposes, letting a web page read a public key and have events signed without ever seeing the private key.

How kind 1 notes thread: the markers on e tags that name the root and the parent, and the q tags that cite another event.

Response caching on the critical endpoints, so a wallet can safely replay a request that a network error interrupted.

How a wallet asks the mint to reissue blind signatures it once received, so a lost wallet can be restored.

How a wallet asks the mint whether a proof is unspent, pending, or already spent.

Kind 2003, a torrent index carrying the info hash, the file list and the trackers needed to rebuild a magnet link.

How to show a token too large for a static QR code as an animated one, using the UR protocol.

The swap operation, where a wallet hands proofs to the mint and receives new blind signatures in return.

Kind 27235, an ephemeral event signed to authorise a single HTTP request.

The content-warning tag, which asks a client to hide an event until the reader chooses to see it.

The subject tag, which gives a note a heading the way an email has one.