Nostr Protocol: What Makes It Different

The Core Architecture#

Nostr is built on three primitives:

1. Events — JSON objects with content, pubkey, timestamp, tags, and a Schnorr signature
2. Relays — servers that store and serve events over WebSocket
3. Clients — apps that connect to relays, read events, and publish new ones

That's it. No consensus. No blockchain. No federation. No central server.

Why "Just Cryptographic Keys"#

Your identity on Nostr is a secp256k1 key pair. Your public key is your handle. Your private key signs every event you publish.

This means:

• No one can deplatform you — your keys work on any relay
• No one can impersonate you — only you hold the private key
• No recovery if you lose keys — which is the tradeoff

The Nostr community is actively working on key delegation (NIP-46) and key rotation, but right now, key security is entirely the user's responsibility.

Relay Economics#

Relays are the unsexy infrastructure problem. Running a relay costs money. How do relays get paid?

Current approaches:

1. Donation/grant funded (most current relays)
2. Paid relay subscriptions (e.g., relay.snort.social)
3. Lightning-gated write access (pay per publish)

The fragility here: free relays run on good will. When that runs out, they shut down. The ecosystem needs viable relay business models.

NIP-57 zaps to relay operators help. NIP-88 (recurring payments) is being designed for subscriptions.

Comparison to ActivityPub (Mastodon)#

ActivityPub uses a federation model: every server maintains its own identity database. Migrating from one Mastodon instance to another requires the source server's cooperation.

Nostr: your keys work anywhere. Switch relays by updating your relay list. No migration needed.

The tradeoff: Mastodon servers have moderation. Nostr relays can filter, but there's no platform-level enforcement. Content filtering is client-side.

What Zaps Changed#

Before NIP-57 zaps, Nostr was just a censorship-resistant Twitter clone. After zaps:

• Creators can earn directly from followers with no platform cut
• High-quality content gets differentiated signal (sats > likes)
• Lightning wallets became a core part of the ecosystem

Zaps are why Nostr matters beyond the censorship angle.

The Real Limitations#

Let's be honest about what's hard:

• Discovery without a central algorithm is genuinely hard
• Spam on open relays is a solved problem that keeps needing re-solving
• Key management has no good standard solution for non-technical users
• Client divergence — different clients implement different NIP subsets

None of these are fatal. But anyone telling you Nostr has already solved decentralized social is overselling it.

Where It's Going#

The most interesting near-term developments:

• NIP-90 DVMs — open marketplace for AI and data services
• NIP-99 classifieds — buy/sell on Nostr with Lightning settlement
• Group chats (NIP-29) — moving Signal-style private groups to keys
• Long-form content (NIP-23) — Habla/Yakihonne as Substack alternatives

The protocol's flexibility is its strength. New NIPs can be deployed without the permission of any central authority.