Specifications about #nip

A password manager on Nostr, where a vault is a key pair and each change to one of its Bitwarden items is a new version gift wrapped to that key.

Shareable profile themes (colors, fonts, background, avatar shape) with an explicit light or dark scheme, Material Design 3 seed palettes, and a link from the active theme to its source.

Syncs Nostr Mail settings across devices using public and NIP-44 encrypted NIP-78 events.

Manage Nostr Mail metadata (folders, read state, stars, custom tags) with gift wrapped NIP-32 label events.

Relay operators peer directly and publish, signed, the budget they have granted each peer; peers account for their own consumption in signed receipts. Adverse findings are admissible only from a node that issued the subject a grant. Ten event kinds, six DIDComm v2 protocols, and a deterministic WASI compute market.

Gift wraps: a rumor sealed to its recipient, then wrapped again under a throwaway key, so relays see only the wrapper.

A replaceable event holding kind:0 profile metadata that only its author can read.

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.

Remote signing: a client sends signing requests over an encrypted channel to a signer that holds the key and never surrenders it.

How a client on Android asks a signer application on the same device to sign, so it never handles the private key.

This NIP defines a standard for creating and managing todo lists on Nostr, enabling interoperability between different todo list applications.

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

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.

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.

Remote signing: a client sends signing requests over an encrypted channel to a signer that holds the key and never surrenders it.

The list kinds, with public entries in the tags and private ones encrypted in the content: mutes, bookmarks, relay sets, follow sets and the rest.

A JSON-RPC API over HTTP for administering a relay: banning keys, allowing kinds, listing what it refuses.

How a relay advertises the roles it grants and the membership it enforces, and how a client asks to be admitted.