Pubky

• Name: Pubky
• URL: https://pubky.org/
• Category: public-key web protocol / decentralized identity-and-routing infrastructure / homeserver-backed application stack / payment-coordination substrate
• Tags: bitcoin-ecosystem
• Summary: Pubky is public-key identity and routing infrastructure with a homeserver stack attached. The social-app framing is downstream. The important surface is PKARR-based discovery, homeserver portability, capability-style app auth, and the still-emerging payment-coordination layer riding on the same identity rail. The named operator boundary above the current product packaging and rollout shell now lives in synonym.
• What it does:
  • Provides an open protocol for per-public-key backends that lets applications authenticate users with cryptographic keys instead of centralized accounts or passwords
  • Uses PKARR plus the Mainline DHT to map a user’s public key to a chosen homeserver, enabling identity-based routing and migration between storage providers
  • Ships a homeserver implementation, SDKs, and REST-style storage APIs so developers can build decentralized apps with standard web-style availability patterns
  • Frames credible exit as a core design goal, letting users keep identity keys, back up data, and repoint their identity to a new homeserver if an operator misbehaves
  • Supports an application layer that already includes Pubky App, Ring, Nexus, and other ecosystem services for publishing, identity management, indexing, and moderation
  • Exposes Paykit as a work-in-progress payment protocol for discovering and coordinating Bitcoin onchain, Lightning, and future payment methods through the Pubky identity layer
• Key claims:
  • The Pubky knowledge base frames the project as a key-based web architecture built around interoperable hosting, censorship resistance, and credible exit rather than around a single flagship app
  • The Pubky Core introduction describes a protocol stack with public-key authentication, capability-style authorization, homeserver discovery, REST-style APIs, and SDKs across Rust, JavaScript, iOS, and Android
  • The same materials say users can repoint identity to a new homeserver through PKARR updates, which is the strongest signal that Pubky is really routing-and-portability infrastructure
  • The security model is refreshingly explicit that the design goal is to reduce trust by preserving user keys, backups, and exit paths instead of pretending operators disappear
  • The pubky-core README reinforces the backend picture: per-public-key backends, third-party authorization, and an HTTP key-value storage API for application builders
  • The Paykit docs are still early, but they already show the intended expansion: payment discovery and coordination for Bitcoin onchain, Lightning, and later methods over the same public-key identity rail
• Whitepaper: No canonical standalone Pubky whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official knowledge base, the Pubky Core introduction, the security model, the Paykit docs, and the pubky-core README; see ../whitepapers/pubky-primary-sources-2026-05-04.md.
• Sources:
  • https://pubky.org/
  • https://docs.pubky.org/
  • https://docs.pubky.org/Explore/PubkyCore/Introduction
  • https://docs.pubky.org/Explore/PubkyCore/SecurityModel
  • https://docs.pubky.org/Explore/Technologies/Paykit
  • https://github.com/pubky/pubky-core
  • https://raw.githubusercontent.com/pubky/pubky-core/main/README.md

Internal linkages

• Company / operator boundary for the current product packaging and roadmap shell: synonym.
• Best identity-and-app-stack contrast when the app graph matters more than portable homeservers: farcaster.
• Best wallet-session comparison when the question is app authorization over an existing wallet rather than a broader public-key web substrate: walletconnect-auth.

Protocol / company boundary

• Keep this note on the protocol and substrate layer: PKARR-based discovery, homeserver portability, capability-style app authorization, HTTP-style backend semantics, and the early Paykit payment-coordination path above that identity rail.
• Use synonym when the sharper question is who is packaging Pubky beside Bitkit, Paykit, and other company surfaces, staffing the teams, and defining the broader product-story rollout path around the protocol.
• That split matters because how does Pubky route identity and preserve exit? and which named operator is currently commercializing and bundling Pubky into a wider Bitcoin-native roadmap? are related but not identical questions.

Control surface

• The protocol-layer leverage sits in PKARR resolution, homeserver choice, backup and migration paths, app-authorization defaults, and whichever indexing or moderation layers users treat as the normal way to discover people and content.

• Paykit may eventually matter more, but today it is still secondary to the identity-and-routing machinery underneath it.

• For the current company-shaped rollout, product framing, and cross-product packaging shell above those mechanisms, read synonym.

• Last reviewed: 2026-08-12 UTC