Frequently Asked Questions

Nostr (Notes and Other Stuff Transmitted by Relays) is a simple, open protocol that enables global, decentralized, and censorship-resistant social media. Unlike traditional platforms, Nostr doesn't rely on a central server - instead, it uses a network of relays that anyone can run.

Unlike Twitter/X which is centrally controlled, or Mastodon which is federated but can still ban servers, Nostr is truly decentralized. Your identity is a cryptographic key pair that you control, and you can publish to multiple relays. No single entity can ban you or censor your content across the entire network.

Both Nostr and Bluesky aim for decentralization, but with key differences. Bluesky uses the AT Protocol with DNS-based identities and a single company running infrastructure. Nostr uses cryptographic keys for identity and anyone can run relays. Nostr has no central authority, while Bluesky's company still controls the main servers.

No, Nostr itself is free and open source. Most Nostr clients and relays are also free to use. However, some premium relays may charge a small fee for enhanced features or spam protection, and some clients may offer optional premium features.

Getting started is simple: 1) Choose a Nostr client (like Damus for iOS, Amethyst for Android, or Primal for web), 2) The client will generate a key pair for you, 3) Save your private key securely (you can't recover it if lost!), 4) Start following people and posting content.

A relay is a server that stores and distributes Nostr events (posts, reactions, etc.). When you publish content, it goes to relays you're connected to. When you want to see content, your client fetches it from relays. You can connect to multiple relays for redundancy.

NIPs (Nostr Implementation Possibilities) are the technical standards and specifications that define how Nostr works. They describe different features and capabilities, from basic event formatting (NIP-01) to advanced features like Lightning payments (NIP-57). Think of them as the building blocks of the protocol.

An event is the basic unit of data in Nostr. Everything is an event: posts (kind 1), profile metadata (kind 0), follows lists (kind 3), reactions (kind 7), and more. Each event is cryptographically signed by the author's private key, making it impossible to forge.

Event kinds are numbers that identify different types of content in Nostr. Kind 0 is profile metadata, kind 1 is short text notes (like tweets), kind 3 is contact lists, kind 4 is encrypted DMs, and kind 30023 is long-form articles. Different clients support different kinds.

Individual relays can choose to delete content, but since your content is typically stored on multiple relays, complete deletion is difficult. You can request deletion (NIP-09), but there's no guarantee all relays will comply. This is part of Nostr's censorship-resistant design.

An npub (Nostr public key) is your public identity on Nostr, similar to a username. It starts with 'npub1' and is derived from your private key. You can share your npub freely - it's how others find and follow you. Example: npub1abc123...

An nsec (Nostr secret key) is your private key - the master password to your Nostr identity. It starts with 'nsec1' and must be kept completely secret. Anyone with your nsec can post as you and access your encrypted messages. Never share it or enter it on untrusted websites.

NIP-05 is a verification system that links your Nostr identity to a domain name. It creates human-readable addresses like name@domain.com instead of long npubs. It proves you control both the Nostr account and the domain, adding credibility and making you easier to find.

You can: 1) Use a free service like nostr.directory or Alby, 2) Buy one from paid providers like Nostr Plebs, 3) Set up your own by adding a .well-known/nostr.json file to your website. Your own domain provides the strongest verification.

Your 'account' is your private key (nsec). Save this securely - write it down, store it in a password manager, or use multiple backup methods. Without your private key, you lose access permanently. Your public key (npub) identifies you but can't be used to post - think of it like a username.

No. There is no password reset or recovery option for Nostr. If you lose your nsec, you lose access permanently. This is why backing up your private key is critical. Some clients offer mnemonic seed phrases (12/24 words) which are easier to backup than raw nsec strings.

Signing extensions (like nos2x, Alby, or Nostr Connect) store your private key securely and sign events for you. Instead of pasting your nsec into every client, the extension handles signing. This is much safer than entering your nsec directly into web apps.

Yes, you can create as many key pairs as you like. Each is a separate identity. Some clients like Amethyst support switching between multiple accounts. You might use different accounts for personal, professional, or anonymous purposes.

Zaps are Bitcoin Lightning payments sent directly to Nostr users as tips or appreciation. When you 'zap' someone, you're sending real money - usually small amounts called satoshis (sats). Zaps appear publicly on posts, creating a value-for-value content model.

You need a Lightning wallet that supports LNURL or Lightning Address. Set your Lightning address (like you@getalby.com) in your profile settings. Most clients have a dedicated field for this. Popular options include Alby, Wallet of Satoshi, and Phoenix.

NIP-57 defines the zap specification - how Lightning payments work on Nostr. It ensures zaps are publicly verifiable and linked to specific posts or users. This allows zap amounts to be displayed and ranked, creating transparent monetization.

No, Bitcoin/Lightning is completely optional. You can use Nostr without any cryptocurrency. However, zaps add a fun social element and enable creators to monetize content directly without ads or subscriptions.

Popular options: Alby (browser extension), Wallet of Satoshi (mobile, custodial), Phoenix (mobile, non-custodial), Mutiny (mobile, self-custodial), and Zeus (mobile, connects to your own node). Choose based on your security and convenience preferences.

By default, zaps are public and show who sent them. However, some clients offer anonymous zapping where your identity isn't revealed. The Lightning payment itself provides some privacy, but the Nostr event recording the zap is typically public.

Value-for-value (V4V) is a content model where creators give freely and audiences pay what they think it's worth. No paywalls, subscriptions, or ads - just direct support via zaps. Popular on Nostr and in the Bitcoin/podcast community.

There's no right amount - zap what you feel content is worth. Common amounts range from 21 sats (a Bitcoin meme number) to thousands of sats for exceptional content. Even small zaps are appreciated and visible.

Nostr provides pseudonymity by default. Your identity is tied to a cryptographic key pair rather than personal information. However, you can choose to verify your identity using NIP-05. Your posts are public unless encrypted (NIP-04/NIP-44 for direct messages).

Nostr uses public-key cryptography to verify identity and sign messages, making impersonation extremely difficult. However, your security depends on keeping your private key safe. Use a dedicated Nostr key, not keys from other applications. Consider using key management tools or browser extensions for better security.

Direct messages using NIP-04 are encrypted, but metadata (who is messaging whom) is visible. The older NIP-04 encryption has known weaknesses. NIP-44 provides improved encryption. For truly private communication, consider additional privacy tools.

NIP-44 is the newer, more secure encryption standard for Nostr, replacing NIP-04. It provides better security properties and supports additional features. Client support is growing - check if your client uses NIP-44 for maximum DM security.

Relays can see encrypted message metadata (sender, recipient, timestamp) but cannot read the encrypted content without your private keys. However, they can observe communication patterns. Choose trusted relays for sensitive communications.

Use a fresh key pair, avoid linking to real identity, use Tor or VPN, don't reuse npubs across contexts, be careful about metadata in images, and avoid NIP-05 verification with identifiable domains. Consider using different keys for different purposes.

Nostr Connect allows remote signing - your private key stays on a secure device (bunker) while you use Nostr from other devices. The signing device approves events without exposing the key. Great for high-security setups.

Not if people verify signatures. Every Nostr post is cryptographically signed. The only way to impersonate you is to steal your private key. NIP-05 verification helps others confirm they're following the real you.

It depends on your platform and needs. iOS: Damus or Nos. Android: Amethyst or Primal. Web: Primal, Snort, or Coracle. For power users: noStrudel. For long-form content: YakiHonne or Habla. Try several to find your preference.

Yes! Your Nostr identity works across all clients. Your posts, follows, and data sync through relays. You can use Damus on iPhone, Primal on web, and Amethyst on Android - all with the same account. This is a core feature of Nostr.

Each client is built by different developers with different priorities. Some focus on simplicity (Nos), others on features (Amethyst), performance (Primal), or communities (Coracle). This diversity is healthy - choose what fits your needs.

Signer apps (like Amber on Android or Keystache on iOS) store your private key securely and sign events for other apps. This is safer than entering your nsec into multiple apps. The signer handles all key operations.

Yes! Notedeck (from Damus team) is available for macOS, Windows, and Linux. Gossip is a privacy-focused desktop client. Most web clients also work excellently in desktop browsers. YakiHonne and some others offer dedicated desktop apps.

Various models: Damus has Purple memberships, Snort has subscriptions, some accept donations/zaps, and Primal offers premium features. Most are open source passion projects. Supporting your favorite clients helps keep them running.

Nos (iOS) and Primal (all platforms) are designed for easy onboarding. Damus is polished and intuitive for iOS users. For Android, Primal offers a smooth introduction. Start simple and explore more advanced clients later.

Habla is a Nostr client focused on long-form content (NIP-23). It's like Medium or Substack but decentralized. Perfect for blogging, articles, and newsletters on Nostr. Your content is stored across relays, not on a company's servers.

Most clients come with sensible defaults. Popular free relays include relay.damus.io, nos.lol, and relay.nostr.band. Consider: reliability, speed, geographic location, and policies. Mix of large public relays and smaller specialized ones works well.

Free relays are open to everyone but may have spam. Paid relays charge for access (reducing spam), offer better uptime, and often have more storage. Some relays are invite-only or have specific community focuses.

Yes! Running a relay is a great way to contribute to Nostr. Options range from lightweight implementations (strfry, nostream) to full-featured (nostr-rs-relay). You can run for personal backup, family, community, or public use.

Your content published to that relay might become temporarily unavailable. However, since you should publish to multiple relays, your content remains accessible from others. This redundancy is core to Nostr's resilience.

Individual relays can moderate their content, but since you publish to multiple relays, content usually remains available somewhere. This is fundamentally different from centralized platforms where a single ban removes everything.

nostr.watch is a monitoring service that tracks relay health, uptime, and NIP support. It helps you find reliable relays and understand which features each relay supports. Great for relay discovery and debugging connection issues.

5-10 relays is a good balance. Too few reduces redundancy; too many slows things down. Include a mix: a few major public relays, maybe a paid one for reliability, and any community-specific relays relevant to your interests.

Different relays support different NIPs (protocol features). NIP-50 enables search, NIP-42 enables authentication. Check relay documentation or nostr.watch to see what features each relay supports.

Yes! Nostr works globally, including in the UK. Given concerns about the Online Safety Act and online censorship, many UK users are exploring Nostr as a censorship-resistant alternative. The protocol's decentralized nature makes it resistant to regional restrictions.

Using Nostr is legal. Like any communication tool, you're responsible for what you post. The protocol itself is neutral technology - similar to email or the web. The Online Safety Act doesn't ban protocols, though it does regulate platforms.

Yes, there are UK-based relays. Running relays locally can improve performance for UK users. Check nostr.watch for relay locations. You can also run your own UK relay to contribute to local infrastructure.

The UK Nostr community is growing! Search hashtags like #NostrUK, follow UK-based accounts, and join Nostr communities focused on UK topics. Many Bitcoin meetups also have Nostr users.

Absolutely! Businesses can use Nostr for censorship-resistant announcements, customer engagement, and building communities. The protocol supports verification (NIP-05), payment integration (Lightning via NIP-57), and long-form content (NIP-23). Several businesses and creators already use Nostr professionally.

NIP-47 lets Nostr apps connect to your Lightning wallet for payments. Instead of copy-pasting invoices, apps can request payments directly. Your wallet approves transactions. Makes zapping and payments seamless across clients.

DVMs are Nostr-native services that perform tasks for payment. Request translation, AI processing, image generation, or other services - pay with Lightning and receive results. It's a decentralized marketplace for computational services.

Nostr has no governance body. Changes happen through rough consensus via NIP discussions on GitHub. Anyone can propose a NIP. Clients and relays choose what to implement. This organic approach has pros (no central control) and cons (slow coordination).