All specifications

One event kind for recording verified handoffs of physical or digital assets on Nostr. A custody transfer event records each handoff; custody evidence is...

Two addressable event kinds for competitive offer-and-selection workflows on Nostr — multiple providers publish offers in response to a request, and the...

Two addressable event kinds for gathering agreement from multiple parties on Nostr — a proposer publishes a consensus proposal listing required voters and a...

Two addressable event kinds for gating workflow progression on Nostr — a proposer publishes a gate requiring sign-off, and one or more designated reviewers...

Two addressable event kinds for declaring credential requirements and revoking credentials on Nostr. NIP-CREDENTIALS completes the credential lifecycle by...

Two ephemeral event kinds for privacy-preserving geospatial presence and location sharing on Nostr. Publishers broadcast coarse-grained presence beacons for...

This nip describes a method by which static websites can be hosted under public keys using specialized host servers

Nostr lacks a standardized, interoperable way to make, track, and revoke truthfulness claims about Nostr events.

Create and manage secure access to your applications using your Nostr identity — without passwords, emails, or centralized user databases.

This NIP defines a protocol for signed attestations of service or task completion between Nostr identities, forming a portable, queryable reputation layer. It...

Blind authentication tokens, which let a mint restrict access to registered users without learning which one is calling.

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.

A protocol for private, encrypted productivity workspaces synced via Nostr relays. All content is end-to-end encrypted with NIP-44 before leaving the client —...

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

This specification defines how to handle large emails (MIME > 65KB) by storing encrypted MIME messages on Blossom servers. Small emails remain stored inline in...

Defines a decentralized ownership model for blobs where multiple pubkeys can be owners, anyone can become an owner, and blobs may be deleted when no owners...

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

This document defines the protocol for managing email metadata (folders, read state, stars, custom tags) in Nostr Mail using NIP-32 labels.

NUT-13 from the Cashu protocol defines how a wallet must generate deterministically its secrets on token creation. This allows wallets in case of any loss to...