Technical specifications, signed and public

SKC defines formats for storing a Nostr secret key on an ISO/IEC 7811 magnetic-stripe card:

My Tasks

This NIP defines a way to share color palettes captured from beautiful moments, enabling pre-verbal visual communication through color and emotion.

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.

OpenPGP public keys are published and unpublished with `PUT` and `DELETE` on their Web Key Directory (WKD) lookup URL, authenticated by NIP-98. The lookup itself is standard WKD.

This NIP defines an addressable event for a place: a physical point of interest such as a restaurant, hotel, museum, shop or park. A place event carries a...

This NIP proposes a minimal structure for representing cards, tasks, updates, and wishes using Nostr events.

NoorNote is a privacy-first Nostr client for desktop (macOS/Linux), Android and web. This is its public capability profile: the Nostr event kinds it can create and/or render. Directories and other clients can read the k-tags below to discover that NoorNote supports a given kind.

This NIP defines two addressable event kinds for representing funded didactic projects (and their byproducts) on Nostr, and delegates the third byproduct —...

This NIP defines a system for publishing controlled vocabularies, taxonomies, thesauri, and classification schemes as Nostr events. It is inspired by SKOS...

This NIP defines how to handle the metadata profile "Allgemeines Metadatenprofil für Bildungsressourcen" (AMB) in nostr:

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.

A document for trying things out: comment, react, fork, anything.

{"name":"Bitswarm","summary":"BT+LN+Nostr swarm protocol + thick client","bundle":"https","formerly":"satswarm","includes":"nwc_pay.js"}

A relay MAY answer single client commands over plain HTTP, beside its websocket. A request carries one command frame, exactly as a client would send it on the...

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.

This NIP defines a standard mechanism for traditional HTTP web pages to advertise their corresponding Nostr entity (such as a NIP-23 long-form article or a...

This NIP defines a list of image proxies that a user would like clients to use when fetching images on their behalf.

Schedule signed Nostr events for future publication through a Scheduler DVM, with the content and publication time hidden from relays.

This is defined as a specification that allows NIP-78 to be used without authentication.

This NIP specifies online identities whose private key can be created in cold storage and stay there permanently. The key never has to touch an...

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.

This NIP defines continuous-integration events for NIP-34 repositories.

Specification for Nostr ebooks, magazines, and other curated publications.

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.