Read the standard by the consequence.

This is the base contract: event shape, signatures, filters and the client-relay conversation every other standard assumes.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP belongs in the NIP map because it gives one piece of Nostr behavior a shared shape instead of leaving each app to invent it alone.

This NIP belongs in the NIP map because it gives one piece of Nostr behavior a shared shape instead of leaving each app to invent it alone.

This standard touches identity and signing: names, keys, links, permissions or external references become easier to carry across apps.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP belongs in the NIP map because it gives one piece of Nostr behavior a shared shape instead of leaving each app to invent it alone.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This is the public social graph: who you follow, how clients rebuild your people layer, and why portability also exposes relationship metadata.

This maps a public key to a DNS-based name. It gives you a readable handle without turning identity back into a platform login.

This is the browser signer doorway. It decides whether a web app can request signatures without ever seeing your private key.

This gives Nostr its shareable prefixes: npub, nsec, note, nevent, naddr and the link forms people actually paste into clients.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This moves signing away from the website or app. Remote signing changes the trust boundary around every sensitive click.

This standard shapes conversation: who can read, who can reply, which room stores context and how privacy survives across clients.

This standard touches identity and signing: names, keys, links, permissions or external references become easier to carry across apps.

This standard shapes conversation: who can read, who can reply, which room stores context and how privacy survives across clients.

This lets a relay describe itself: name, contact, software, limits, payment hints and policy cues before a client depends on it.

This is relay authentication. It explains how a relay can ask a client to prove control of a key before accepting or serving data.

This standard affects availability and discovery: how clients find relays, authenticate, search, sync or manage infrastructure.

This standard affects availability and discovery: how clients find relays, authenticate, search, sync or manage infrastructure.

This helps clients find where a public key expects to read and write. Relay discovery becomes personal instead of guessed.

This standard affects availability and discovery: how clients find relays, authenticate, search, sync or manage infrastructure.

This brings Negentropy-style sync into the NIP map, so relays and clients can compare sets without shipping everything first.

This standard affects availability and discovery: how clients find relays, authenticate, search, sync or manage infrastructure.

This is the modern private-message stack: gift-wrapped events, rumor structure and the migration away from older direct-message habits.

This standard affects availability and discovery: how clients find relays, authenticate, search, sync or manage infrastructure.

This is versioned encryption for payloads. It is the privacy standard you read when encrypted content needs modern primitives and clear limits.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This standard shapes conversation: who can read, who can reply, which room stores context and how privacy survives across clients.

This standard shapes conversation: who can read, who can reply, which room stores context and how privacy survives across clients.

This turns long-form writing into addressable Nostr events, so articles can move beyond one publishing client.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This standard shapes conversation: who can read, who can reply, which room stores context and how privacy survives across clients.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This standard gives publishing and media a portable form instead of locking creative work inside one client.

This is Nostr Wallet Connect. It gives apps wallet permissions without turning every payment flow into full wallet custody.

This is zaps: the Lightning payment receipt and social signal that made value visible inside Nostr conversations.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This NIP changes how value moves through Nostr: offers, requests, receipts, wallet permissions or payment context become signed data.

This standard turns governance into explicit records: reports, labels, badges, polls or community boundaries you can inspect.

This standard turns governance into explicit records: reports, labels, badges, polls or community boundaries you can inspect.

This makes badges portable. The hard part is not the badge image; it is issuer identity, provenance and display rules.

This standard turns governance into explicit records: reports, labels, badges, polls or community boundaries you can inspect.

This standard turns governance into explicit records: reports, labels, badges, polls or community boundaries you can inspect.

This standard turns governance into explicit records: reports, labels, badges, polls or community boundaries you can inspect.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP belongs in the NIP map because it gives one piece of Nostr behavior a shared shape instead of leaving each app to invent it alone.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This NIP defines event behavior that clients and relays need to interpret consistently, especially around kinds, tags and product consequences.

This signs HTTP requests with Nostr keys. Read it when a website or API wants authentication without a normal account password.