The protocol that promised to liberate social media from billionaire control is eating itself alive. Key maintainers are walking away. The chain reaction began spinning last week, and almost nobody outside its tightest circle saw it coming until it was too late.

The Scream That Broke the Timeline

A post that landed on the Nostr-native forum Oddbean this week read less like a hot take and more like a distress call. It was a cascading confession from a builder who had watched the protocol’s internal machinery seize up in slow motion.

“Right now I am watching Nostr fragment before my very eyes. Developers are giving up, because they have very little leadership, direction, or can collectively agree on anything that would improve the situation,” the anonymous developer wrote. “Our market share is diminishing. People leave every day due to either broken clients, or lack of engagement. If we do not find a way to come together NOW as a community to improve upon our situation … Then we are going to die a slow painful death as a protocol.”

Within hours, the note had ripped across Nostr relays, drawing hundreds of threaded replies — some defensive, many vindicated, and a handful so raw they read like breakup letters to an idea that once seemed inevitable.

This was not the usual Beltway punditry about whether decentralization “scales.” This was a public scream from inside the machine, and it landed at the worst possible moment. Jack Dorsey’s open-protocol bet, Nostr, the system he anointed as the censorship-resistant backbone of a new social web — and on which he just launched the buzzy Vine-reboot app Divine — is breaking along the very fault lines its architects insisted could never fracture.

Two Protocol Splits, Zero Roadmap

The Oddbean confession was not an isolated flare. Since the first week of May, a broader governance crisis has consumed Nostr’s developer channels, with two overlapping disputes reaching boiling point simultaneously.

The first is NIP-26, a proposed specification for delegated event signing that allows users to temporarily hand signing authority to third-party services. Originally written to accommodate a corporate integration with Minds.com, NIP-26 has become a proxy war. Opponents, including the protocol’s creator fiatjaf, have publicly declared it “a bad idea that will eventually destroy Nostr,” arguing it introduces architectural complexity that undermines the platform’s core simplicity. Supporters counter that key rotation and delegation are non-negotiable for mass adoption. Neither side has budged, and the pull request has languished for months.

The second, and arguably more existential, conflict revolves around the outbox model — the architectural proposal meant to wrestle Nostr away from the gravitational pull of a handful of mega-relays. Right now, an estimated 90 percent or more of Nostr users connect to a few massive relay servers, making the network vulnerable to pressure from governments, hosting providers, and coordinated attacks. The outbox model promises to decentralize content distribution by making clients smarter about which relays they query, but critics warn it will degrade performance and fragment the user experience so severely that adoption becomes impossible. As one developer on the thread put it, nostr “seems likely” to split into two separate networks — a simple vanilla protocol and a complex, untested alternative called negentropy — within months.

“We just have a bunch of people bitching on their own that Nostr is dead,” the Oddbean poster continued, “instead of manning and womaning up to patch our shit and get to work.”

From Open Protocol to Walled Garden — In Theory

The deepest wound, however, may be ideological. Nostr was designed to be permissionless: nobody can stop anyone else from building. Yet that same openness has produced what one long-time contributor described as “a kind of Nostr ‘shadow governance’ — a sort of cool kids club that decides, without much public discourse, what is in and what is out.”

When a protocol has no formal governance model, decisions about which NIPs get merged, which proposals get ignored, and which maintainers hold sway become intensely personal. Resentments compound. Developers who pour months into a rejected NIP drift away. The pool of people willing to do the grinding, unglamorous work of maintaining relays and fixing client bugs shrinks by the quarter.

I have covered open-source governance struggles for over a decade, and what I see in Nostr today follows a depressingly familiar pattern. A founding visionary prizes simplicity above all else, but simplicity alone cannot coordinate the logistics of a living, breathing network that now spans more than 315,000 profiles and 228,000 daily events.

“I think nostr may already be doomed for two reasons,” wrote one prominent community voice. “Reason one is the misaligned incentives of note copying … So we can never fix this, and nostr will always be centralized in practice … Reason two is that the seed culture of nostr was far too monolithic: bitcoiners.”

Jack Dorsey’s $10 million donation to the ecosystem, once hailed as a lifeline, has not quieted these concerns. In fact, the launch of Divine — built on Nostr but controlled by a single nonprofit — has sharpened the question: if the protocol’s most visible showcase is a centralized app, is Nostr a protocol or a marketing strategy?

Bear and Bull Cases for Nostr

Bear Case

The structural incentives point toward continued centralization. Relay operators cannot cover costs, driving network participants onto a shrinking number of large servers. Governance remains informal and exclusionary, accelerating developer flight. The NIP-26 and outbox deadlocks persist, fragmenting the protocol into incompatible dialects. Major clients like Damus face app-store pressures that force compromises on core principles. If the current trajectory holds, Nostr could lose relevance to Bluesky’s AT Protocol — which already boasts millions of users — and become a niche playground for a shrinking circle of bitcoin maximalists.

Bull Case

Crashes clear deadwood. The current crisis could finally force the governance reckoning the community has avoided for years. A formalized, transparent NIP process built on community voting — as proposed in the Oddbean thread — might restore developer confidence and accelerate innovation. The outbox model, if implemented with proper client support, could meaningfully distribute relay dependency. And Divine’s traction could become an onboarding funnel that introduces millions of new users to Nostr’s underlying architecture. If the community treats this fracture as a catalytic reset rather than a death sentence, Nostr’s best days may still lie ahead.

Summary

Nostr promised that protocols could replace platforms, that cryptographic keys could substitute for corporate accounts, and that a garden of interoperating clients would flourish where walled gardens once stood. This week, that promise met its most serious internal challenge yet. The protocol is not dead, but it is bleeding talent and coherence at a rate that should alarm anyone who has invested time, code, or identity into its ecosystem. The builders sounding the alarm are not trolls — they are the people who have been running the relays, writing the NIPs, and fixing the clients. Their message is brutal but clear: Nostr must govern itself or it will dissolve itself, not by external attack, but by internal entropy.