Gozzip: Your Social Graph Is Infrastructure.
Human social networks are the result of millions of years of evolution. The way we form trust, propagate information, preserve what matters, and forget what doesn’t — these aren’t arbitrary behaviors. They’re deeply optimized mechanisms that no engineering team has come close to designing from scratch.
And yet, when we build digital social networks, we ignore all of it.
We replace the trust graph with a follower count. We replace contextual reputation with a global score. We replace community memory with a database owned by a company. We replace the natural redundancy of people who care about each other with a server that may or may not stay online.
Nostr got identity right. But the social graph still exists as data, not as infrastructure. Your WoT — the follows, the mutual connections, the mute lists you and your network have built together — is a display layer. It filters your feed. It doesn’t hold your data.
What it’s never been asked to do is what it was always capable of: act as a highly resilient, self-organizing, trust-weighted distribution system. Reciprocity, redundancy, contextual reputation, proportional propagation — evolution built all of this in. We’ve been routing around it.
Gozzip is a protocol that finally builds on what’s already there. It inherits Nostr’s proven primitives — secp256k1 identity, signed events, relay transport — and adds the layer that makes the social graph load-bearing: your trust network becomes your infrastructure.
How it works
In Nostr, your Web of Trust (WoT) is the graph of people you follow and who follow you back, also shaped by who you’ve chosen to mute, and who your network has collectively decided to exclude. Trust is defined in both directions — by whom you vouch for and by whom you, together with your community, have found worthy and unworthy of attention.
The core mechanism is a storage pact: a bilateral agreement between two peers in your WoT to hold each other’s data. Volume-balanced, cryptographically verified, maintained quietly in the background. Your pact partners receive a copy of your events alongside your relays. When someone reads your content, they check the pact network first. The relay is still there — it’s just no longer the load-bearing wall.
Retrieval cascades through four tiers: local pact storage, cached endpoint, WoT-filtered gossip with daily-rotating blinded pubkeys, and relay fallback as last resort. Each tier only activates if the previous one fails. In practice, the vast majority of reads never leave the first tier.
Because every event is signed by your keys, it’s self-authenticating wherever it lives — on your device, on a pact partner’s node, or converted to ActivityPub or AT Protocol for federation elsewhere. The data is yours independent of where it’s stored or what protocol it travels over.
It works with existing Nostr relays today. No relay modifications. No new infrastructure to run. All protocol intelligence lives in the client.
The transition
You start exactly where you are now. As mutual follows accumulate, pacts form silently. Storage starts distributing. If a relay goes down, the data still exists, held by people with bilateral obligations to keep it — not a company, not an operator, your WoT.
Over time, the read path shifts. Relay usage decays naturally as pacts mature. The relay’s role changes from gatekeeper to discovery layer — useful for reaching outside your trust graph, not required for the data that already lives within it.
No flag day. No migration. No moment where users are asked to do anything. The sovereignty accrues in the background, by default.
Where things stand
The architecture is sound. The protocol primitives are specified. The theoretical foundations — small-world network properties, epidemic spreading bounds, Dunbar-calibrated parameters, fault tolerance guarantees — are worked out in the whitepaper.
What remains is engineering. Real-world network density versus theoretical graph models. Whether the full-node ratio emerges organically from social incentive alone. Optimal challenge frequency on mobile. Known unknowns with known approaches — the kind of problems you solve by shipping.
The relay doesn’t die. It earns a more honest role. And the Web of Trust — the one you’ve already built — becomes the infrastructure it always should have been.
Read the whitepaper: <https://github.com/gozzip-protocol/gozzip>
What’s being built now
The first client is already in progress — not a power-user tool, but a proper node designed for everyone. Simple, unintimidating, and capable. The kind of thing that gives ordinary users the sovereignty this protocol was designed for, without asking them to understand why.
If you want to discuss the protocol, contribute to the spec, or help build, reach me out.
Write a comment