What is Nostr?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
Nostr is an open, decentralised communication protocol where users control their own identity through cryptographic keys, publish signed messages to independently operated "relay" servers, and can never be deplatformed — because no single company owns or controls the network.
The social media censorship problem
Twitter, Facebook, and YouTube are centralised platforms — they control who can post, what can be seen, and what accounts can exist. When a platform bans an account, that person's audience, history, and content disappears. Platform moderation policies are opaque, inconsistent, and subject to political and commercial pressures. Users have no recourse and no ownership of their accounts.
Nostr (Notes and Other Stuff Transmitted by Relays) is a response to this. It was created pseudonymously (by "fiatjaf") in 2020 and gained significant traction in 2022-2023 when Jack Dorsey (Twitter's founder) donated 14 BTC to its development and promoted it as a Twitter alternative.
How Nostr works
In Nostr, your identity is a cryptographic key pair — a private key (which you keep secret) and a public key (your Nostr address). You sign all your messages with your private key. Your messages are published to "relays" — simple servers that store and forward signed messages. Any server can be a relay. You can publish to multiple relays simultaneously. Anyone can read from any relay.
Because your identity is your key (not an account on a company's server), you can never be permanently banned. If one relay removes your content, you continue on others. Your followers subscribe to your public key, not to your account on a specific platform.
The Bitcoin connection
Nostr has deep integration with Bitcoin and Lightning Network. The Zap protocol (NIP-57) allows Lightning payments within Nostr — clicking "zap" on a post sends satoshis directly to the author via Lightning. This creates a monetisation model for content that bypasses advertising, subscriptions, or platform payments. Nostr has no native token.
Is Nostr a financial asset?
Nostr itself has no token and is not a VDA. Bitcoin/Lightning used within Nostr apps follows standard BTC tax treatment in India.
🟡 A bit more detail
For when you want to go a little deeper.
Relays — the Nostr network architecture
A Nostr relay is a simple WebSocket server that accepts signed events from clients and serves them back. Relays are not federated (like Mastodon) and do not need to communicate with each other — a client connects to multiple relays simultaneously and merges their content. Relays can be public (accepting everyone), paid (requiring a small fee to prevent spam), or private (for specific communities). Running a relay is technically straightforward — several open-source implementations exist (nostr-rs-relay, strfry, Nostream). Anyone with a VPS can run a relay.
Nostr has developed a significant ecosystem. Damus (iOS) and Amethyst (Android) are the most popular Nostr client apps. Primal.net provides a web client with content discovery. Notable users include Jack Dorsey, Edward Snowden, and a growing community of Bitcoin-aligned users who value censorship resistance. Nostr is used for short-form posts (Twitter-equivalent), long-form articles (Substack-equivalent), direct messages, and live streaming. The Zap economy — Lightning payments between Nostr users — has created a new model where high-quality posts earn satoshis directly from readers rather than from advertising platforms.
NIPs — Nostr Implementation Possibilities
Nostr is specified through NIPs — documents describing specific protocol features. NIP-01 defines the base protocol: events (signed JSON objects), event kinds (integers specifying message type), and the relay communication protocol. NIP-04 defines encrypted direct messages. NIP-57 defines Zaps (Lightning payments). NIP-90 defines Data Vending Machines (computational tasks requested via Nostr and paid via Lightning). The NIP process is open — anyone can propose a NIP, and relay/client developers choose which NIPs to implement.
Key Nostr metrics: number of active users, relay count, client diversity, Zap volume (Lightning payments within Nostr), and developer activity (new NIPs and clients). Nostr is deliberately simple — this simplicity makes it robust and easy to build on, but also limits some features that centralised platforms provide (no algorithmic recommendations, no central moderation, limited spam resistance). The tradeoff is explicit: censorship resistance over convenience. Live data: Nostr.band · Nostr.info.
🟣 The full technical picture
For the technically curious.
The Nostr event structure
Every piece of content in Nostr is an "event" — a JSON object with these fields: id (32-byte SHA-256 hash of the serialised event), pubkey (32-byte hex public key of the author), created_at (Unix timestamp), kind (integer specifying event type), tags (array of arrays for metadata and references), content (the event's payload), sig (64-byte Schnorr signature over the event id). The event id is computed deterministically from the other fields — it cannot be forged. The sig proves the pubkey holder created this event. Relays verify the signature before accepting events. Clients verify signatures before displaying content.
Source: Nostr NIPs (Nostr Implementation Possibilities). github.com/nostr-protocol/nostr · NIP-01: github.com/nostr-protocol/nips/01.md
Zaps — Lightning payments in Nostr
NIP-57 defines the Zap protocol. A Zap is a Lightning payment from one Nostr user to another, linked to a specific Nostr event. The flow: (1) sender requests a Lightning invoice from the recipient's LNURL server, specifying which Nostr event they are zapping; (2) recipient's LNURL server generates the invoice and returns a zap request; (3) sender pays the Lightning invoice; (4) recipient's LNURL server broadcasts a "zap receipt" event to the recipient's relays; (5) clients display zap receipts on the original post with the amount. Zaps are visible on-chain (Lightning payment) and linked to the post (Nostr event) — creating public attribution of value to content.
Nostr uses Schnorr signatures on the secp256k1 curve — the same curve used by Bitcoin. This is not a coincidence: Nostr keys are compatible with Bitcoin keys. A user's Nostr identity (nsec/npub) uses the same cryptographic primitives as a Bitcoin wallet. Some wallets (Alby, Zeus) combine Bitcoin Lightning and Nostr identity in a single key pair, allowing a user's Lightning payment address and their social identity to be derived from the same seed. This design choice means Nostr inherits Bitcoin's well-audited cryptographic library ecosystem.
Key facts
- Type: Decentralised social communication protocol
- Identity: Cryptographic key pair (Schnorr, secp256k1)
- Infrastructure: Relays (WebSocket servers, anyone can run)
- Specification: NIPs (open, community-driven)
- Payment integration: Zaps (NIP-57, Lightning Network)
- No token: Nostr has no native cryptocurrency
- Creator: fiatjaf (pseudonymous), 2020