The Complete Nostr Guide: Decentralized Social Media for Bitcoiners
The Complete Nostr Guide: Decentralized Social Media for Bitcoiners
Nostr (Notes and Other Stuff Transmitted by Relays) has become the social layer for much of the Bitcoin community. Understanding why it works, how it’s different from traditional social media, and how to use it effectively is essential knowledge for 2026.
Why Social Media for Bitcoiners Matters
The Bitcoin community has always relied on social platforms for coordination, education, and dissemination. BitcoinTalk in the early days. Twitter from 2011-2023. These platforms worked — until they didn’t.
Twitter’s 2022-2023 chaos — the acquisition, the verification changes, the ban waves, the arbitrary content moderation — demonstrated that centralized platforms are fundamentally unstable for communities that have enemies. Governments can pressure companies. Companies can ban accounts. The platform owner can change the rules overnight.
For a community whose primary use case is resisting monetary censorship, social media censorship is an existential threat. Nostr solves this with a simple, elegant design.
The Core Design: Simplicity as Strength
Nostr’s architecture is almost insultingly simple. There are two components:
Relays: Servers that accept and store Nostr events (notes, likes, follows). Anyone can run a relay. Relays are commodity infrastructure — they just store and forward.
Clients: Applications that connect to relays to read and write events. Anyone can build a client. The client is what users interact with.
Keys: Your identity is a private key. Every action is signed by your private key. There’s no username, password, or account — just a key pair.
The flow: you write a note, sign it with your private key, and send it to any relay. Anyone who wants to read your notes subscribes to relays you’re posting to. That’s it.
Public Keys as Identity
Your Nostr identity is your public key (npub). The private key never leaves your device. Anyone who knows your npub can find your notes — if your relays allow public access.
The npub is a bech32-encoded string:
That’s 63 characters. Impractical for sharing. This is where NIP-19 comes in.
NIP-19: Human-Readable Identifiers
NIP-19 adds support for npub-derived identifiers:
- (full public key)
- (compressed profile reference)
- (compressed article/note reference)
But the most important addition is NIP-05 — the ability to map public keys to DNS-based identifiers.
NIP-05: The DNS Identity Layer
NIP-05 maps public keys to identifiers like . The format is an email-style address where the domain resolves to a JSON file containing the public key.
When you follow :
- Your client queries
- The server responds with Alice’s public key
- Your client subscribes to notes from that key
The power: your identity is tied to your domain name, not to Nostr itself. If Nostr disappears tomorrow, your identity still exists if you control that domain.
For businesses and publications: NIP-05 lets you issue verified identities to employees. means the person posting is actually a Forbes reporter. This is how Nostr can support verified journalism.
The Relay Ecosystem
Running a relay is trivial — it’s a simple server. Hundreds exist. Key relay characteristics:
- Some are public (anyone can post)
- Some are invite-only
- Some require payment
- Some are curated (only certain kinds of content)
- Some are geography-specific
Your choice of relay doesn’t define your identity — it just determines where your notes are stored. You can post to multiple relays simultaneously. Your followers can subscribe to you from any relay.
The relay operator has no power over your identity: they can ban your content, but your key pair remains. You post to another relay, your followers follow you there.
The Client Landscape
Clients are where the UX lives. The major options in 2026:
Damus: The original iOS/Android client. Full-featured, active development, well-integrated with Lightning tipping.
Iris: Known for excellent UX and friend-finding features. Popular among new Nostr users.
Coracle: Web-based, accessible without installing an app. Good for trying Nostr casually.
Snort: Minimal, fast, focused on power users. Excellent for those who want keyboard shortcuts and advanced features.
Primal: A curated experience with algorithmic content discovery. More like Twitter’s feed and less like a chronological list.
Amethyst: Open-source Android client with good features and regular updates.
The Bitcoin Integration: Zaps
NIP-57 defines Lightning zaps — the feature that makes Nostr unique among social platforms. Zap receipts are Lightning payments bundled with Nostr notes.
When you zap someone:
- Your Nostr client creates an invoice for the zap amount
- Your LN wallet pays the invoice via Lightning
- The zap is recorded on Nostr as an event with the zap receipt
The recipient’s client displays the zap. Zap amounts are typically 21, 42, 1000, 10021, or 21000 sats — the amounts are meaningful to Bitcoiners.
The economic model: content creators can earn sats directly from readers. No platform takes a cut. No advertising. No subscription. The platform is infrastructure; the value flows directly between creator and consumer.
The Privacy Properties
Nostr provides meaningful privacy improvements over centralized social media:
Identity persistence: Your npub is the same across every client and relay. There’s no “account” that can be banned — just a key pair.
Censorship resistance: No single relay or client controls your identity. If bans you, your notes are still on and .
Metadata minimization: Relays don’t know what other relays you use. Clients don’t know which relays your followers use. The network graph is not centralized.
But privacy isn’t perfect:
- Your IP address when posting is visible to your relay (use TOR or a VPN for better privacy)
- If your NIP-05 identifier links your npub to your domain, your identity is partially linkable
- Chain analysis can correlate your Nostr activity if you’ve used an exchange-linked Lightning wallet
Building on Nostr
For developers, Nostr’s simplicity makes it an excellent platform:
NIP-04: Encrypted direct messages between users NIP-18: Reposts (shares/retweets) NIP-26: Delegated signing — let someone else post on your behalf with limited scope NIP-28: Community notes / hashtags / threads NIP-40: Expiration timestamps — notes that delete themselves after a set time NIP-65: Relay list metadata — tell others which relays you’re posting to
The ecosystem is building: blog platforms (highlighter.to, blogstack), marketplaces (nos.market), video platforms, podcasting tools, and more.
Key Takeaways
- Nostr’s identity = private key = portable and uncensorable
- Relays are commodity storage with no power over your identity
- NIP-05 maps npubs to DNS identifiers like @alice@bitcoinmagazine.com
- Lightning zaps enable direct creator compensation without platform intermediaries
- Privacy is better than centralized social media but not perfect — use TOR for stronger anonymity
⚡ If this was useful, a zap is always welcome. tomford@rizful.com
Write a comment