The Great Fracturing That Wasn’t

In early May, the headlines were brutal. “Nostr Enters Its Great Fracturing as Developers Sound the Alarm,” one outlet proclaimed. The protocol that promised to liberate social media from billionaire control was allegedly eating itself alive. Key maintainers were at odds. The narrative was clear: decentralization had failed, again.

I watched this unfold with a mixture of concern and skepticism. Having followed Nostr since its early days, I’ve seen this pattern before—the crypto community’s tendency to pronounce projects dead at the first sign of growing pains. What the doomsayers missed, however, was the quiet, relentless work happening beneath the surface.

Fast forward to this week, and the picture couldn’t be more different.

The Grants That Signal a Pivot

On July 14, a technical analysis piece dropped on CoderLegion, examining Nostr’s viability as an out-of-the-box backend. But the real story emerged from the OpenSats announcement of the Seventeenth Wave of Nostr Grants. Five projects received funding—four of them first-time grantees—and the list reads like a roadmap for protocol evolution:

• 44Billion: A browser-based app launcher with an app store for discovering and installing Nostr applications. Think of it as an open, uncensorable alternative to the Apple App Store or Google Play.

• NosCall: An encrypted audio and video calling app built in Flutter, using WebRTC for real-time media. Private communication has long been one of Nostr’s most important use cases, and real-time calls add a familiar way for users to communicate through identities they already control.

• AI marketplace protocol: Connecting AI clients and providers through Nostr discovery and bitcoin-native payments.

• Polished mobile client: Abstracting the complexity of Nostr and Lightning for first-time users.

This isn’t just funding—it’s a strategic bet on usability. The Nostr Fund is signaling that the protocol’s future lies not in preaching decentralization to the converted, but in building products that ordinary people actually want to use.

The Developer Activity You’re Not Seeing

While the media focused on drama, developers were shipping code at a remarkable pace.

On July 5, Swift Nostr released version 0.6.0—a massive protocol and tooling update adding ten new NIPs (Nostr Implementation Possibilities), including NIP-13 for Proof of Work, NIP-46 for remote signing, and crucially, a spec-compliance fix to NIP-44 encryption. The fix matters: previously, Swift Nostr’s encryption payloads didn’t match other clients. Now they do.

The Perl ecosystem saw similar activity. Net-Nostr-Core 1.001000 dropped on July 3, providing core protocol and NIP tooling. Net-Nostr-Relay 1.001001 followed on July 6, verifying Schnorr signatures over the 32-byte event ID instead of its hex string—ensuring the relay accepts events signed by standard Nostr implementations.

Perhaps most significantly, NIP-ee was published on July 9, proposing E2EE messaging using the Messaging Layer Security (MLS) Protocol. The goal? Private and confidential direct messages and group messages with forward secrecy and post-compromise security. “Without proper E2EE, Nostr cannot be used as the protocol for secure messaging clients,” the NIP states. The ambition is clear: Nostr wants to become the decentralized Signal.

Where Nostr Fits (And Where It Doesn’t)

The CoderLegion analysis from July 14 offers a sober, balanced perspective that deserves attention. The author makes a compelling case: Nostr is a ready-to-use, decentralized backend. It gives you an event model, signatures, encryption, and sync through relays. For notes, private chats, and simple feeds, it covers almost everything—with no server of your own.

But here’s the catch: once you need a smart feed, roles, hierarchies, or complex moderation, the protocol hits one basic limit—only the owner of a key can change an event. After that, the extra workarounds quickly cost more than they save.

In my experience, this is the most honest assessment of Nostr I’ve read. It’s not a panacea. It’s a tool with clear strengths and equally clear limitations. The teams receiving grants understand this—they’re building applications that play to Nostr’s strengths rather than fighting its weaknesses.

The Bear and The Bull

The Bear Case:
Nostr’s user activity flatlined since late 2025. The protocol remains niche, with a steep learning curve that scares away mainstream users. The “Great Fracturing” narrative, while overblown, reflects real tensions in the community. And for all the development activity, killer apps remain elusive. The grants are promising, but promising and delivering are two very different things.

The Bull Case:
The infrastructure is maturing rapidly. The Swift Nostr release alone added support for ten new NIPs—that’s ten new capabilities developers can build on. The MLS-based E2EE proposal addresses the protocol’s biggest security gap. The grants are funding exactly what Nostr needs: onboarding tools, real-world applications, and bridges to non-technical users. The developer activity is real, measurable, and accelerating.

Summary

Nostr is at an inflection point. The narrative of “fracture” was premature—what we’re actually witnessing is a protocol growing up. The grants announced this month aren’t about keeping the lights on; they’re about building the on-ramps that will determine whether Nostr remains a niche experiment or becomes the decentralized communication layer the internet desperately needs.

The developers shipping code this week understand something the pundits don’t: protocols win not through ideology, but through utility. NosCall, 44Billion, and the other grant recipients are building utility. The question isn’t whether Nostr will survive—it’s already proven it can. The question is whether it can thrive.

Based on what I’ve seen this week, I wouldn’t bet against it.