Cowrie Research

pubky-primary-sources-2026-05-04

3 min read

Pubky primary sources — 2026-05-04

Project status in this pass

  • No canonical standalone Pubky whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official knowledge base plus the Pubky Core introduction, the security model, the Paykit work-in-progress docs, and the pubky-core README.
  • The project is best understood as public-key identity-and-routing infrastructure with a homeserver-backed application stack and an emerging payment-coordination layer rather than as only a social app or alternative DNS tool.

Primary-source snapshots

1) Official knowledge base

  • URL: https://docs.pubky.org/
  • Key excerpt:
    • The knowledge base says Pubky includes Pubky Core, PKARR, and Pubky App and is still a work in progress.
    • It says Pubky aims to unlock the web through a key-based, self-regulating architecture that combines decentralized routing and identity with interoperable hosting, censorship resistance, and credible exit.
    • It also lists infrastructure such as homeservers, Ring, Nexus, moderation, explorer tooling, and Homegate, which suggests a broader stack than a single end-user app.

2) Pubky Core introduction

  • URL: https://docs.pubky.org/Explore/PubkyCore/Introduction
  • Key excerpt:
    • The introduction calls Pubky Core an open protocol for decentralized web applications and an open protocol for per-public-key backends for censorship-resistant web applications.
    • It says the stack combines a public-key-based alternative to DNS with standard web technologies, public-key authentication, capability-based authorization, homeserver discovery, and RESTful API standards.
    • It describes three main components: the protocol specification, a homeserver implementation, and SDKs across Rust, JavaScript, iOS, and Android.
    • It also explicitly lists payment infrastructure and points to Paykit as a future payment-coordination layer.

3) Security model

  • URL: https://docs.pubky.org/Explore/PubkyCore/SecurityModel
  • Key excerpt:
    • The security model says Pubky aims to minimize trust requirements while remaining practical and centers the design around credible exit.
    • It explains that users keep cryptographic identity keys, use PKARR as the authoritative routing layer, and can migrate away from a misbehaving homeserver without losing identity.
    • It also describes planned data signing, encrypted data, and mirroring improvements, which is useful for understanding what is already shipped versus still aspirational.

4) Paykit docs

  • URL: https://docs.pubky.org/Explore/Technologies/Paykit
  • Key excerpt:
    • The page says Paykit is a decentralized payment protocol built on Pubky and is currently under active development and not production-ready.
    • It aims to enable payment discovery, negotiation, and coordination across Bitcoin onchain, Lightning Network, and potentially other methods.
    • It says a static Pubky public key is intended to become a universal payment identifier, with recipients publishing payment methods through their homeserver.
    • This is the strongest evidence in this pass that Pubky should still be treated as crypto-adjacent infrastructure despite not being a payments-first project today.

5) pubky-core README

  • URL: https://raw.githubusercontent.com/pubky/pubky-core/main/README.md
  • Key excerpt:
    • The README describes Pubky Core as “An open protocol for per-public-key backends for censorship resistant web applications.”
    • It highlights public-key-based authentication, third-party authorization, and a key-value store exposed through a PUT/GET/DELETE HTTP API.
    • It also shows that the repository ships both a homeserver and SDK, reinforcing that Pubky is operating infrastructure for builders rather than only publishing a conceptual protocol.

Working conclusion

Pubky is best cataloged as public-key identity, routing, and application infrastructure with a Bitcoin-adjacent payment-coordination roadmap. The deciding evidence in this pass was the combination of PKARR-based discovery, homeserver-backed storage and migration, credible-exit-focused security language, developer SDKs and HTTP APIs, and the explicit Paykit effort to map Bitcoin and Lightning payment discovery onto the same identity substrate.

Graph View