What Happened This Week In The Nostr World

You probably still think Nostr is just another decentralized Twitter clone that peaked in early 2025. The W3C Nostr Community Group just published did:nostr v0.1.0 as an official draft report—with over 30 implementations already in the wild. But that’s only half the story. While centralized platforms stumbled through global outages, the protocol quietly finalized three major NIP updates in five days. Yet here’s what nobody’s telling you: the most ambitious proposal of the bunch—the one that was supposed to bring Signal-level encryption to Nostr—has already been replaced. And the window to understand what’s actually happening is closing faster than you think.

The Irony Wasn’t Lost on Anyone Watching

This week, the contrast between centralized and decentralized social infrastructure couldn’t have been starker. While Instagram and Facebook suffered worldwide outages, leaving millions scrambling, something different was happening in the quieter corners of the internet.

Nostr—the decentralized protocol that’s been steadily gaining traction since Jack Dorsey threw his weight behind it—was pushing through a significant week of technical development. From June 23 to June 24, three major NIPs reached final status and were moved into NIP-01, the protocol’s foundational specification.

But that’s not the whole story. On July 9, a much more ambitious proposal emerged—one that aimed to solve Nostr’s long-standing encryption problems. And then, almost as quickly as it appeared, it was effectively dead on arrival.

The Three That Made It

Three NIPs crossed the finish line this week. NIP-16, governing event treatment—essentially answering the question of how long an event matters when it hits a relay—was marked final mandatory on June 24. NIP-12, covering generic tag queries, followed the same path, giving clients a predictable way to ask relays for indexed tag values. And NIP-33, which defines parameterized replaceable events (renamed to “addressable events”), also reached final status on June 23.

In my experience covering protocol development, this kind of foundational consolidation matters more than flashy features. These aren’t the headlines that grab attention—they’re the plumbing. And plumbing is what separates protocols that survive from those that fade.

The Encryption Elephant—and Why It’s Already Dead

Then came NIP-ee.

Published on July 9, this proposal aimed to bring end-to-end encrypted messaging to Nostr using the Messaging Layer Security (MLS) protocol—essentially the evolution of the Signal Protocol. The rationale was compelling: “Without proper E2EE, Nostr cannot be used as the protocol for secure messaging clients”. By replacing centralized servers with decentralized relays, the NIP argued, “we make it nearly impossible for a centralized actor to completely stop communications between individual users”.

The proposal addressed real problems. NIP-04, the original direct message standard, “leaks significant amounts of metadata”. NIP-17, while better, “doesn’t solve forward secrecy or post compromise security”. NIP-ee promised to fix all of that—forward secrecy, post-compromise security, group messaging at scale.

But here’s the catch. The NIP carries a prominent warning: “unrecommended: superseded by the Marmot Protocol”.

The Marmot Protocol repository merged a significant PR on July 3, changing its status from “draft for internal review” to “adopted”. By the time NIP-ee was published on July 9, it was already obsolete. The encryption problem isn’t being solved by NIP-ee—it’s being solved by something else entirely.

The Bigger Story Everyone’s Missing

Meanwhile, the W3C Nostr Community Group published did:nostr v0.1.0 as an official draft report this week, with over 30 implementations already in the wild. This isn’t just another technical specification—it’s Nostr positioning itself as a serious decentralized identity system.

Jack Dorsey continues to loom large 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. When someone who built one of the world’s largest social platforms says that, it’s worth paying attention. The timing is also telling. As centralized platforms experience outages and policy controversies, the contrast between the old model and the new one becomes increasingly stark.

What This Means Going Forward

The technical groundwork being laid suggests Nostr is transitioning from experimental protocol to production-ready infrastructure. The three NIPs that reached final status this week address developer experience and protocol consistency. The did:nostr draft opens the door to identity use cases beyond social media.

But the NIP-ee situation reveals something else: the protocol is moving fast, and not every proposal survives contact with reality. The encryption problem isn’t solved yet—it’s just been punted to a different solution.

Nostr faces the same challenge every decentralized protocol encounters: adoption friction. The learning curve remains steep. Client fragmentation is a real concern. And while the NIPs are technically sound, they’re only valuable if clients actually implement them.

Summary

Nostr just completed a significant week of protocol development. Three major NIPs—NIP-16, NIP-12, and NIP-33—reached final status between June 23 and June 24 and were moved into NIP-01. The W3C Nostr Community Group published did:nostr v0.1.0 as an official draft report with over 30 implementations already in the wild. A fourth proposal, NIP-ee, was published on July 9 with ambitious goals for end-to-end encryption—but carries an explicit warning that it’s been superseded by the Marmot Protocol.

I think we’re watching a protocol mature in real-time. 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.