What is Nostr? A plain-English guide for 2026

Most people find Nostr when they are annoyed at something. A post got a reach penalty. An account got suspended for a joke that a moderation bot did not parse. A platform changed the rules quietly and shipped yet another feed nobody asked for. At some point you start looking around and thinking there has to be a different shape for this.

Nostr is that different shape. It is a protocol, not a product, which is the part that trips up most newcomers. You do not sign up for Nostr. You pick an app, generate a pair of keys on your own device, and start posting to a handful of servers that agree to relay your messages. No company sits in the middle. No phone number, no email, no KYC, no "by using this service you agree" clause.

When you are ready, grab your @nostr.blog address →

This guide is the orientation we wish existed when we first looked at Nostr. It answers the four questions everyone actually has. What it is, how it works, why it exists, and what it costs you to try.

What Nostr actually is

Nostr stands for Notes and Other Stuff Transmitted by Relays. It is an open protocol for publishing short pieces of signed data to a network of small, independent servers called relays. That description sounds abstract so here is the concrete version.

When you write a post, your app attaches a signature made with your private key. It then sends the post to a list of relays you choose. Each relay stores the post and forwards it to anyone who subscribes to it. Your followers' apps connect to the same relays (or different ones), fetch your posts, verify the signatures, and show them on a timeline.

That is the whole protocol. There are extensions for direct messages, long-form articles, reactions, payments, profile metadata, and dozens of other features. Every one of them is built on the same pattern: signed data, published to relays, fetched by clients.

The protocol was written in late 2020 by a developer named fiatjaf and published as a tiny specification on GitHub. By April 2026, there are several hundred thousand active accounts, over 800 public relays, and more than 60 clients across iOS, Android, web, and desktop.

Why it is built that way

Nostr's design is a direct response to a problem most social platforms refuse to fix: your identity is owned by the platform, not you. If Twitter decides your account should disappear, it disappears. If Meta changes its terms, you either accept them or leave and lose your followers with you.

On Nostr, your identity is a cryptographic key pair that lives on your device. Apps cannot freeze it. Relays cannot delete it. If the relay you post to decides they do not like you, you publish to a different relay and your followers' apps pick up your posts there. The social graph is portable because it lives in your own signed contact list event, not in a platform database.

The tradeoff is that Nostr does not try to solve every social-media problem the way a centralized platform does. Spam prevention, search, content moderation, abuse reporting. These become things that happen at the client or relay level, by people choosing policies, not a single platform enforcing one rule for everyone. Some users find this liberating. Others find it overwhelming. Both reactions are legitimate.

How a post actually travels

The vocabulary gets easier once you see the sequence end to end. Say you write "hello Nostr" on your phone.

1. Your client turns that text into a JSON object called an event. The event includes the content, a timestamp, your public key, and a list of any tags (mentions, hashtags, replies).
2. Your client signs the event with your private key. The signature proves the event came from the holder of that key pair.
3. Your client connects to each of your configured relays over a WebSocket and sends the signed event.
4. The relays accept the event (or reject it, based on their own policies) and store it.
5. Anyone who is subscribed to events tagged with your public key, meaning your followers, gets the event pushed to their client in real time. Users who open a client later fetch it on demand.
6. Every client that receives the event verifies the signature before showing it. A forged event with the wrong signature is silently dropped.

No step in this sequence depends on a single company. If any relay goes offline, the event still lives on the others. If you change clients, you keep the same keys and the same social graph.

What you need to actually use it

Three things, in order of commitment.

An app. A client is just software that knows how to send and receive Nostr events. Good starting points on mobile are Damus on iOS and Amethyst on Android. On the web, Primal and our own nostr.blog client are the easiest onramps.

A key pair. Every Nostr client will generate one the first time you open it. The private key (the one that starts with nsec) signs your posts. Keep it safe the way you keep a password manager master key. Losing it means losing the account forever, because there is no "forgot your password" flow when nobody has your password.

A readable name. The raw public key looks like npub1pf8hkx3.... Technically it works, but it is impossible to share at a bar. You can attach a human-readable handle to your key using a standard called NIP-05, something like alice@nostr.blog or you@yourdomain.com. A NIP-05 on the nostr.blog domain starts at $2.99 per year for longer names, with premium short names priced higher.

The honest tradeoffs

Nostr is not a finished product. A few things are real pain points in 2026, and skipping them would be a disservice.

Direct messages are encrypted but the sender and recipient are visible to relays. If you need private messages that hide who is talking to whom, Nostr is not the right tool yet. There is ongoing work on this (NIP-44, NIP-17 gift wraps) but adoption is partial.

Search is awkward. There is no Google of Nostr. If you want to find a post from three months ago you had better remember which client you used and hope it cached it. Some relays offer search, others do not.

Spam is a live problem on permissionless platforms. Most clients now ship mute lists and web-of-trust filters, but the first hour on a fresh account can still feel like nobody is home except bots.

Onboarding has been clunky for years. Downloading a key, understanding why you need it, copying it to a second device. These steps have scared away plenty of would-be users. The nostr.blog signup flow was built specifically to make this less painful. You sign up with a normal-looking handle and we quietly handle the cryptographic stuff in the background.

So is it worth trying

If you already liked what an open protocol for social looked like on paper, yes. Nostr is the closest thing we have to it running today. If you are arriving because a specific platform made you angry last week, spend an hour poking around first before you commit. The social graph on Nostr is smaller than the one you are leaving, and the quirks are different. But the tradeoff is real. Your account cannot be taken away, your followers come with you, and nobody behind the curtain is "optimizing engagement" at your expense.

If you want the shortest path from curiosity to posting, the signup below takes about two minutes and gives you everything you need on one page. An identity, a wallet, and a client.