The decentralized social protocol just dropped four major updates in a single week. While Big Tech’s centralized platforms keep stumbling, Nostr is quietly building the infrastructure for something far more resilient. Here’s why the developers building on this protocol think 2026 is the year it all comes together—and what these new NIPs mean for the future of online communication.

The irony wasn’t lost on anyone watching.

On June 23, Instagram and Facebook suffered a worldwide outage, leaving millions scrambling. The next day, Twitter—now X—experienced its own disruption. Centralized social media, once again, proved its fragility.

Meanwhile, in the quieter corners of the internet, something different was happening. Nostr—the decentralized protocol that’s been steadily gaining traction since Jack Dorsey threw his weight behind it—was pushing through its most aggressive week of technical development in months.

From June 20 to June 24, the Nostr Improvement Proposals repository saw a flurry of activity that signals a protocol maturing faster than many anticipated.

The NIP Avalanche

Four major NIPs either reached final status or received significant updates in just five days.

NIP-16, governing event treatment, was marked as “final mandatory” and moved into NIP-01 on June 20. NIP-12, covering generic tag queries, followed suit on June 21. These aren’t flashy features—they’re the plumbing. But in my experience covering decentralized protocols, it’s precisely this kind of foundational work that separates projects that survive from those that fade.

More intriguing is NIP-a4, which defines “kind24” as a new public messaging format. The specification describes it as a “simple plaintext message to one or more Nostr users”—but there’s a catch. The NIP explicitly states that “there is no concept of a chatroom” and that messages “can start and continue without any syntactic connection to each other”.

Why does this matter? Because it represents a philosophical choice. Instead of replicating the group chat models we’re all accustomed to, Nostr is leaning into its core strength: simplicity. Kind24 isn’t trying to be Discord or Telegram. It’s trying to be something new—a public messaging layer that exists outside the constraints of traditional social platforms.

The End-to-End Encryption Elephant

Perhaps the most significant development came from NIP-ee, which tackles end-to-end encrypted messaging using the Messaging Layer Security protocol.

Here’s the context: Nostr’s current direct messaging solutions—NIP-04 and NIP-17—have real limitations. NIP-04 leaks metadata. NIP-17, while better, doesn’t provide forward secrecy or post-compromise security. As the NIP authors bluntly state: “Without proper E2EE, Nostr cannot be used as the protocol for secure messaging clients”.

The proposed solution adapts MLS—essentially the evolution of the Signal Protocol—for Nostr’s architecture. This isn’t just about better encryption. It’s about making Nostr viable for serious, private communication at scale.

What strikes me about this NIP is its ambition. The authors aren’t just fixing a bug. They’re positioning Nostr as a genuine alternative to centralized messaging platforms. “By replacing centralized servers with decentralized relays,” the NIP argues, “we make it nearly impossible for a centralized actor to completely stop communications between individual users”.

Dorsey’s Shadow Looms Large

Jack Dorsey continues to cast a long shadow over the protocol. In early June, the former Twitter CEO named Nostr alongside Tor and Bitcoin as one of only three “scalable censorship-resistant technologies” currently available. He’s been vocal about his belief that open protocols like Nostr represent the future of social media.

This matters beyond the obvious celebrity endorsement. Dorsey understands the centralized internet’s vulnerabilities better than almost anyone. When he says Nostr belongs in the same sentence as Bitcoin and Tor, it’s worth paying attention.

The timing is also telling. As centralized platforms experience outages and policy controversies—Twitter recently announced it would remove accounts created solely to promote other platforms, including Nostr—the contrast between the old model and the new one becomes increasingly stark.

Looking Promising

The technical groundwork being laid this week suggests Nostr is transitioning from experimental protocol to production-ready infrastructure. The MLS integration for E2EE, combined with the standardization efforts in NIP-16 and NIP-12, addresses two of the most common criticisms: privacy and developer experience.

If these upgrades ship and gain client adoption, Nostr could see accelerated mainstream interest. The protocol’s inherent resistance to censorship, combined with genuinely private messaging, positions it as a compelling alternative for users disillusioned with centralized platforms.

The Bumpy Road Ahead

Nostr faces the same challenge every decentralized protocol encounters: adoption friction. The learning curve remains steep. Client fragmentation is a real concern—as one Nostr user noted, “soon all the social clients will be isolated and incompatible”. And while the NIPs are technically sound, they’re only valuable if clients actually implement them.

The protocol also faces competition from other decentralized social initiatives. If Nostr can’t deliver a user experience that rivals centralized alternatives, technical superiority won’t matter.

Summary

Nostr just completed its most significant week of protocol development in recent memory. Four major NIP updates—including the foundational NIP-16 and NIP-12, the public messaging NIP-a4, and the ambitious E2EE proposal NIP-ee—signal a protocol that’s serious about addressing its limitations.

The backdrop couldn’t be more relevant. While centralized platforms grapple with outages and policy controversies, Nostr is quietly building the infrastructure for something more resilient.

I think we’re watching a pivotal moment. The question isn’t whether Nostr has the technical foundation—this week’s updates suggest it does. The question is whether the ecosystem can translate that technical progress into real-world adoption.

For now, the developers are doing their part. The rest is up to the users.