2026-07-10 –, P2P Portal
Users of Pubky applictations fully own their identity and decide themselves where their data is hosted. Credible exit and optional self-hosting enable full user self-sovereignty.
The fully open-source Pubky protocol only decentralizes where it matters: identity and data. Identity is a public key the user owns. Data lives on a homeserver the user chooses and can migrate at will. Everything else — data presentation, the UI layer — stays in the hands of the application provider and optimizes for a slick user experience.
This 30-minute talk is an introduction to both the concepts and the technology as well as a starting point for building.
We'll cover:
- A closer look at PKARR (Public Key Addressable Resource Records), the protocol Pubky uses for decentralized discovery — built on top of Mainline DHT and used by a growing set of decentralized projects for self-sovereign name resolution: mapping a public key to wherever its data, services, or endpoints actually live, without DNS or central registries.
- How identity, hosting, and discovery fit together end to end: from key generation through DHT lookup to homeserver hosting
- What's already running on the Pubky stack
- How to start building your own Pubky app today: Entry points, examples, and understanding the most important concepts
The goal is to leave the room inspired by a different angle on decentralizing the web. Design choices, working concepts, and ideas worth borrowing into your own projects, whether or not Pubky ends up in your stack.
Software Engineer working for user-sovereignty. I care about anti-authoritarian tech, helping the people building it, and tacos.
