All specifications

Defines the language every other BUD is written in, and what a blob is: raw binary data addressed by the sha256 hash of that data.

This NIP defines event kinds for podcast episodes and trailers on Nostr, enabling decentralized podcast publishing and RSS feed generation.

This NIP defines a protocol for syncing encrypted files (such as notes, documents, and their attachments) across devices using Nostr relays. It enables...

An addressable kind for presentations.

Relays implementing this behavior should accept events dated in the future, but keep them stored in a different bucket so that they aren't revealed to any...

This NIP defines kind 30817 for community-authored NIPs. These events allow users to create, share, and maintain custom protocol specifications that extend or...

Kind 24, a plain text message addressed to one or more keys, meant for a notification screen rather than a thread.

Kind 30402, a classified listing: something for sale or on offer, with enough structure to be worth querying.

An HTTP file storage API discovered through a well-known document, replaced by Blossom.

Kind 1063, file metadata: the url, the hash, the mime type and the size of a shared file.

Data vending machines: paid jobs requested and delivered as events, reserving the kind range 5000 to 7000.

Assertions a trusted provider publishes about a key, an event or an external identifier, so a client does not have to compute a web of trust itself.

Kind 9802, a highlight: the passage someone found worth keeping, pointing back at the event or the URL it was taken from.

Negentropy over Nostr: range-based set reconciliation, so two sides transfer only the events one of them lacks.

Kind 9041, a fundraising goal that zaps are tallied against.

The i tags for identifiers that exist outside Nostr: URLs, ISBNs, podcast GUIDs, DOIs, hashtags and blockchain transactions.

Kind 34550, Reddit-style communities where moderators approve the posts addressed to them.

Video events, long and short, carrying the metadata a video client needs around media hosted elsewhere.

The dash tag, marking an event that only its author may publish, which relays enforce through NIP-42.

Kind 20, picture-first posts where the images carry the event rather than illustrate it.