Bitcoin Privacy

Nostr Protocol Explained: Decentralized Social Media

Feb 12, 2026 · 14 min read · Updated Latest correction
Three separate metal memo clips each hold an identical blank cream note on pale plaster.

The Nostr protocol is an open, decentralized communication protocol that enables censorship-resistant social media, messaging, and content publishing without depending on any single company, server, or platform gatekeeper. Short for “Notes and Other Stuff Transmitted by Relays,” Nostr uses cryptographic key pairs and a network of independent relay servers to let anyone publish and read content without permission from a central authority. For bitcoiners building a sovereignty stack, Nostr fills the communication layer that Bitcoin and Lightning fill for money.

Why Nostr Matters for Bitcoin Users

Bitcoin gives you financial sovereignty — the ability to send and receive value without permission. But communication sovereignty is equally fundamental. If a platform can ban your account, your ability to coordinate, transact, and share information depends on that platform’s continued tolerance of your activity.

Nostr solves this by making your identity portable. Your Nostr identity is a cryptographic key pair (a public key and a private key) — identical in concept to your Bitcoin keys. No company owns your identity, no server hosts your account, and no moderator can permanently silence you. If one relay bans you, you publish through others. Your followers find you through your public key, not through a platform-assigned username.

The integration between Nostr and Bitcoin’s Lightning Network goes deeper than philosophy. Nostr clients support “zaps” — instant Lightning micropayments attached to posts. Instead of clicking a meaningless “like” button, you send actual satoshis to the content creator. This creates a native, censorship-resistant economy where value flows directly between participants with no payment processor in the middle.

How the Nostr Protocol Works

Nostr’s architecture is deliberately simple. It has only two components: clients and relays.

Clients

A client is the application you use to read and write Nostr content — similar to how a browser is the client for the web. Clients can be mobile apps, desktop applications, or web interfaces. Popular clients include:

  • Damus — iOS client, now also free on Android, with a Twitter-like interface and zap support
  • Amethyst — Feature-rich Android client supporting custom emoji reactions, marketplace listings, live streams, and zaps
  • Primal — Cross-platform (web, iOS, Android) with a built-in Lightning wallet on mobile, making zapping seamless
  • noStrudel — Web-based client focused on power users with advanced filtering and relay management
  • Coracle — Lightweight web client with a clean reading experience

You can use multiple clients simultaneously with the same identity — your key pair works everywhere. Switching clients is like switching email apps: your data follows you because it lives on relays, not inside any single application.

Relays

Relays are servers that store and forward Nostr messages (called “events”). Anyone can run a relay — it’s open-source software that accepts events from clients, stores them, and serves them to other clients that request them. Relays are the infrastructure layer, but no single relay is essential. Your client connects to multiple relays simultaneously, so if one goes down or bans you, your content remains available through the others.

Relays can choose their own policies: some accept everything (public relays), some require payment (paid relays that filter spam), and some are invite-only (community relays). This creates a free market for message distribution where relay operators compete on reliability, speed, and moderation quality rather than controlling the protocol itself.

You hold a key pair: a private key (nsec) that signs every post and a public key (npub) that is your identity. Your client publishes each post to several relays. Relay A is down or bans you, drawn dashed; relays B and C still store your posts. Your followers look you up by your npub and read from B or C. If you switch app or lose a relay, your key, identity and followers stay with you.
Your identity is a key, not an account. If one relay drops you, your posts are still on the others, and your followers’ apps find them by your public key.

Events and Signatures

Everything on Nostr is an “event”: a small JSON record (a simple structured text format) holding the content, the author’s public key, a timestamp, a kind number, tags, and an id. The id is a fingerprint (a SHA-256 hash) of those other fields, and the author’s private key signs it; that signature proves the author created the event and that nobody has changed it since. Events are published to relays and can be verified by anyone. The signatures are Schnorr signatures on the secp256k1 curve (BIP-340), the same scheme Bitcoin uses for Taproot transactions. This isn’t a coincidence: it enables tight integration between Nostr identities and Bitcoin/Lightning infrastructure.

Event types (called “kinds”) define different content categories: kind 1 is a short text note (like a tweet), kind 0 is profile metadata, kind 4 is the old encrypted direct message format (NIP-04, now discouraged in favour of NIP-17, which seals each private message inside a kind 1059 “gift wrap” signed with a one-time key), kind 30023 is long-form content (like blog posts). The NIP (Nostr Implementation Possibilities) system defines these standards, allowing the protocol to evolve through community proposals.

An event has seven fields: id, a fingerprint (hash) of the next five; pubkey (who wrote it); created_at (when); kind (what it is, 1 is a short note); tags (replies, mentions, topics); content (the text); and sig, made by your private key signing the id. A relay checks the signature against the public key, then stores and forwards the event, and readers' apps check it too. Change one letter and the id changes, so the signature fails: nobody can alter your post or fake one in your name. Common kinds: 0 profile, 1 short note, 9735 zap receipt, 30023 long article, 1059 gift wrap for new private messages; kind 4, the old direct messages, is drawn dashed: avoid it.
An event is a signed envelope. You don’t have to trust a relay with your words: it can store, forward or drop your post, but it cannot change it. The kind number tells apps how to show it.

Zaps: Lightning Payments on Social Media

Zaps are Nostr’s killer feature for bitcoiners. When you zap a post, your client asks the service behind the author’s Lightning address for an invoice and pays it. The author’s service then publishes a public receipt (a kind 9735 event) to relays. The result: anyone can see the author’s Lightning service report that the zap was paid (its word, not proof of payment), and the author receives actual satoshis — not points, not tokens, not promises.

Three parties: you, the author's Lightning service, and relays with everyone reading. Step 1: your client signs a zap request (kind 9734) and sends it to the author's service, not to relays. Step 2: the service returns an invoice. Step 3: you pay it over Lightning. Step 4: the author's service publishes a receipt (kind 9735) to relays. The receipt is the service saying it was paid, not proof of payment.
A zap is a Lightning payment with a public receipt. Your client never posts the receipt: the author’s Lightning service does, once it is paid. To receive zaps, the author needs a Lightning address in their profile from a service that supports Nostr zaps (NIP-57).

Zaps work because Nostr identities can be linked to Lightning Network addresses. Set your Lightning address in your Nostr profile, and any client that supports zaps can send you sats, provided the service behind that address supports Nostr zaps (NIP-57). Popular wallets like Alby, Wallet of Satoshi, and Primal’s built-in wallet do, and handle the Lightning payment seamlessly.

Emerging features include zap splits (automatically dividing payments between multiple creators), zap-powered polls (vote with sats), and zap-based content ranking where posts surface based on total value received rather than algorithmic engagement metrics.

Setting Up Nostr: Getting Started

  1. Generate your keys. Download a Nostr client (Damus on iOS, Amethyst on Android, or Primal for cross-platform). The app generates your key pair automatically. Your public key (npub) is your identity — share it publicly. Your private key (nsec) is your secret — never share it. Back up your private key the same way you’d back up a seed phrase.
  2. Set up your profile. Add a display name, profile picture, bio, and Lightning address. A Lightning address from a service that supports Nostr zaps (NIP-57) lets other users zap you.
  3. Connect to relays. Most clients connect to a default set of relays automatically. You can add or remove relays based on your preferences — more relays means wider reach, fewer relays means faster performance.
  4. Add a NIP-05 identifier. NIP-05 lets you link a domain name to your Nostr key, giving it a human-readable address. If you own yourdomain.com, you can set up user@yourdomain.com as your Nostr identifier. A matching record only shows that whoever controls the domain linked that name to your key: it identifies you, it does not prove who you are. Treat other people’s NIP-05 addresses the same way.
  5. Start following people and publishing. Follow other users by their public keys, engage with content, and send zaps. Your social graph is portable — if you switch clients, your follows come with you.

Nostr vs Traditional Social Media

FactorNostrTwitter/XMastodon
Account ownershipYou (cryptographic keys)PlatformServer admin
Censorship resistanceHigh (multi-relay)None (platform decides)Partial (server-level)
Identity portabilityFull (key pair works everywhere)None (locked to platform)Limited (migration between servers)
Native paymentsLightning zapsNone nativeNone native
Algorithm controlClient-side (you choose)Server-side (platform controls)Chronological
Data ownershipPublished to chosen relaysPlatform owns dataServer admin controls
Developer opennessFully open protocolAPI increasingly restrictedOpen source

Running Your Own Relay

Like running your own Bitcoin node, running your own Nostr relay gives you maximum sovereignty. Your relay can serve as a personal backup (all your events stored on your own hardware), a community hub (a relay for your local Bitcoin meetup or organization), or a paid relay that charges for access to filter out spam.

Several open-source relay implementations exist: nostr-rs-relay (Rust), strfry (C++), and nostream (TypeScript). A relay runs comfortably on a Raspberry Pi or a small VPS. If you already run an Umbrel or Start9 node, Nostr relay apps are available in their app stores.

Privacy Considerations

Nostr improves on traditional social media privacy in several ways — your IP can be hidden behind Tor, your identity is pseudonymous (a public key, not a name), and no company collects your data for advertising. But it’s not a privacy silver bullet:

  • Public by default: Standard Nostr events are visible to anyone connected to the same relays. Treat public posts as fully public.
  • Metadata: Relay operators can see which public keys publish events and from which IP addresses (unless you use Tor).
  • DMs improved but imperfect: NIP-44 encryption (ChaCha20 with HMAC-SHA256) protects the text of private messages, and NIP-17 wraps each message so that the sender and the real time are hidden. The relay can still see which key a message is addressed to, and so can anyone else unless the relay shows these messages only to their recipient, as NIP-17 asks relays to do. Relays also see the IP address of whoever connects (unless you use Tor).
  • Zaps and Lightning addresses: Every zap receipt is public and shows how much was sent and, for a normal zap, which key sent it. Private and anonymous zaps in Damus and Amethyst sign with a throwaway key instead, so your usual key stays off the receipt. Your Lightning address also links your Nostr identity to your payment activity. Use separate Lightning wallets for zapping and for private transactions if this matters for your privacy model.
A table of what each party sees. A public note and the key that wrote it: anyone on the relay sees it, and so does the relay operator. A normal zap, which key sent it and how much: public, because the receipt is public. Your IP address: hidden from other users, seen by the relay operator unless you use Tor. The text of a private message (NIP-44): hidden from both. Which key sent a private message (NIP-17): hidden from both, though the relay may still guess it from your IP. Which key a private message is for: the relay operator sees it; other users see it too unless the relay shows it only to the recipient, as good relays do. Your Lightning address ties your key to your payments, so zap from a separate wallet if that matters.
Encryption hides what a private message says, not who it is for. The relay also sees where you connect from unless you use Tor. For private conversations, Signal protects this metadata better.

The Nostr Ecosystem in 2026

Nostr has grown far beyond Twitter-like microblogging. The protocol now supports:

  • Long-form content: Blog posts and articles published directly on Nostr (kind 30023), readable by any compatible client
  • Marketplaces: Peer-to-peer selling with Lightning payment integration
  • Live streaming: Video streams with real-time zapping
  • Group chats: NIP-29 defines relay-based groups
  • Git collaboration: Patches, pull requests and issues as Nostr events, with the repositories themselves on Git servers
  • Audio content: Podcasts and audio spaces with Lightning micropayments per minute listened

Jack Dorsey’s significant financial support ($10 million in July 2025 to “and Other Stuff”, an open-source collective that builds on Nostr) has accelerated ecosystem development. The NIP process continues to produce new standards, with the developer community actively proposing and implementing protocol enhancements.

Verdict

Nostr completes the sovereignty stack. Bitcoin gives you monetary sovereignty. The Lightning Network gives you payment speed and privacy. Running your own node gives you transaction verification independence. And Nostr gives you communication sovereignty — the ability to publish, message, and transact socially without any platform’s permission.

The protocol is still maturing. Client UX varies in quality, relay reliability isn’t uniform, and the network effect is smaller than incumbent platforms. But for bitcoiners who already understand the value of holding their own keys and running their own infrastructure, Nostr is a natural extension of the same principles. Your identity is your key pair. Your data lives on relays you choose. And value flows through Lightning, not through advertising.

Frequently Asked Questions

Is Nostr only for Bitcoin users?

No. Anyone can use Nostr for censorship-resistant communication without touching Bitcoin. However, the integration with Lightning (zaps, payments, value exchange) makes it particularly attractive to bitcoiners. The shared cryptographic infrastructure (secp256k1 keys) means your Nostr and Bitcoin keys use the same math, though you should use separate key pairs for security.

What happens if I lose my Nostr private key?

You lose access to that identity permanently — just like losing a Bitcoin private key. There’s no “forgot password” option because no company controls your account. Back up your nsec (private key) the same way you’d back up a seed phrase: write it down, store it securely, and never enter it on untrusted websites or apps.

Can Nostr be shut down?

No single entity can shut down Nostr because there’s no central server, company, or organization that operates it. Individual relays can be shut down, but new relays can be spun up by anyone. Your content and identity persist as long as at least one relay stores your events. This is similar to how Bitcoin can’t be shut down because no single entity controls the network of nodes.

How do I find people to follow on Nostr?

Most clients have discovery features — trending posts, recommended follows, and topic-based feeds. You can also import your Twitter follows if your contacts have published their Nostr public keys. Bitcoin conferences, meetups, and podcasts are strong Nostr communities. You can also search by NIP-05 identifiers (like user@domain.com), but a match only links a name on that domain to a key, so check it is the person’s real domain before you follow.

Is Nostr more private than Signal or Telegram?

For direct messages, Signal provides stronger privacy guarantees (sealed sender, minimal metadata). Nostr’s advantage isn’t in private messaging — it’s in public, censorship-resistant publishing combined with native Lightning payments. Use Nostr for public communication and zaps, and Signal for private conversations where metadata protection matters most.

Filed under: Bitcoin Privacy

Continue Reading

← Back to All Articles