Specifications about #nip

Kind 1040, which carries an OpenTimestamps proof that another event existed before a given Bitcoin block.

Kind 9, a chat message, whose replies are further kind 9 events quoting their parent.

Kind 30078, where an application stores data it has no intention of sharing with any other.

Kind 11, a forum thread with a title, whose replies are NIP-22 comments rather than nested notes.

Kind 30166, relay discovery events published by monitors, describing what a relay claims to be and whether it answers.

The proxy tag, which links an event bridged from another protocol back to the object it came from.

Podcast episodes published as events, so a feed stops depending on one URL staying alive.

Kind 31234, an encrypted draft of an unsigned event of any kind, stored on relays for its author alone.

Kind 30023, long-form articles written in Markdown, addressable so their author can revise them in place.

The emoji tag, which maps a shortcode written in the content to an image URL.

How to write a mention inside content: a nostr: URI in the text, and nothing else demanded of the reader.

The nostr: URI scheme, which turns a NIP-19 entity into a link any client can open.

Kind 30818, wiki articles addressed by a normalised subject, where several people are expected to write about the same one.

The bech32 forms of keys, ids and pointers: npub, nsec, note, nprofile, nevent and naddr.

Calendar events, date-based and time-based, and the RSVPs that answer them.

The COUNT verb, which asks a relay how many events match a filter instead of asking for the events themselves.

Kind 1337, a code snippet carrying its language, its filename, its extension and its runtime.

Kind 1068, a poll with its options, its type and its deadline, answered on the relays it names.

The expiration tag, a timestamp after which relays and clients should treat an event as gone.

Proof of work over an event id, mined with a nonce tag and measured in leading zero bits.