Nostr vs. Pubky Comparison (July 2025)
Nostr is a purpose-built, minimal censorship-resistant social protocol, while Pubky is a public-key-first web backend architecture aiming to extend self-sovereign identity and storage far beyond social media, using more traditional web infrastructure and DNS analogies.
Feature Overview
| Feature | Nostr | Pubky |
|---|---|---|
| Main Purpose | Decentralized social/messaging protocol | Decentralized backend for identity, DNS, storage, messaging |
| Data Model | Signed events (JSON) via relays; non-permanent storage | Key-value store by public key; user/homeserver controls storage |
| Identity (Key Type) | secp256k1 key pair (Bitcoin compatible) | Ed25519 key pair |
| Protocol/API | WebSockets; NIP-specified JSON messaging | RESTful HTTP (PUT/GET/DELETE); language SDKs |
| Authentication | secp256k1 signatures; Schnorr optional | Ed25519 signatures; optional session/token auth |
| Extensibility | NIPs, modular clients/relays | Schemas, CLI/tools, app plugins, PKarr (alt-DNS) |
| Storage/Retention | Relays decide what to store; users can post to many | User/homeserver determines data permanence |
| Censorship Resistance | Anyone can run relays; users can multi-home; resistance at relay layer | Anyone can run/choose homeserver; direct user data control |
| Posting/Media | Text, images, links, files, rich media via extensions | Text, chat, long notes, files, media (all formats supported) |
| Clients | 100+ open-source web, desktop, mobile, and CLI clients | Primarily the official web app at this stage; broader client ecosystem expected as project matures |
| DHT Network | Not used; relays act as message hubs | Integral: DHT underpins PKarr DNS and content discovery |
| Codebase | Multiple language repos; established, active ecosystem | pubky-core (Rust), PKarr, web app; early but open to contribution and extension |
| Customizability | Modular; many forks/clients/relays | Designed for extensibility; true diversity will follow as ecosystem grows |
| Community | Large, distributed, high relay/client diversity | Developer-focused, early user and tool adoption |
| Recent Activity | Ongoing dev, new NIPs, client innovation | Core protocol and DHT/PKarr actively developed; expanding tools and integration |
DHT and Pubky
- Pubky: Uses a DHT for decentralized naming (PKarr), content discovery, and routing, aiming at robust censorship resistance and user autonomy as deployment increases.
- Nostr: Does not use a DHT; relies on multiple independent relays for decentralization.
Takeaways
- Nostr is a mature, established protocol with high diversity in software and participation. Its minimalistic, event-based approach and thriving ecosystem fuel broad adoption and rapid evolution.
- Pubky is an emerging platform building infrastructure for flexible application backends and decentralized naming, with a promising model and clear technical vision—the broader ecosystem is likely to expand as development progresses.
References
Current as of July 2025, per official project repositories and documentation.
No comments yet.
Write a comment