NOSTR MAGAZINE

Nostr’s New P2P NIP Quietly Targets Stablecoin Markets (and It’s Already Live)

Nostr’s development pipeline rarely produces a proposal that ships with a live, revenue-generating implementation on day one. But that’s exactly what happened this week. On November 12, a pull request titled “NIP-XX: Peer-to-peer Order and Trade events for non-Bitcoin assets” appeared in the nostr-protocol/nips repository, authored by Forte11Cuba. By November 13, the PR was public, and by the time most developers saw it, QvaPay had already published its first signed orders on Nostr using the proposed kind 35353 format.

The timing matters. Nostr’s existing P2P standard, NIP-69, was built for Bitcoin-denominated orders. It expresses amounts in satoshis and uses kind 38383. The new proposal deliberately does not extend NIP-69. The author’s reasoning is blunt: reusing NIP-69’s semantics would break existing clients like Mostro, lnp2pBot, RoboSats, and Peach, and it would misread a 250 USDT order as 250 satoshis. Instead, the new NIP defines a separate addressable event kind for crypto assets and platform balances “other than bitcoin,” traded against fiat, with a signed trade document for every execution.

I think this is the most consequential Nostr spec move since the NIP-17 private messaging overhaul, precisely because it targets markets where most P2P volume actually happens: stablecoins in regions with capital controls. QvaPay’s documentation is explicit. The platform’s internal balance, QUSD, is traded against fiat payment methods including Cuban pesos, MLC, Zelle, PayPal, Pix, and SberBank. Every public order and every executed trade is signed with QvaPay’s platform key and published to relays like relay.primal.net and relay.snort.social. No account or API key is required to read the data.


The Liquidity Argument Meets the Governance Question

The immediate catalyst is liquidity fragmentation. NIP-69’s own abstract admits that multiple P2P platforms “contribute to the liquidity split” and that a common standard enables a larger pool. The new proposal applies the same logic to non-Bitcoin assets. By publishing orders as Nostr events, any client can aggregate offers across platforms and compute real rates and volumes from signed executions. QvaPay’s live dashboard already does this for its own market, and the format is designed to be read by anyone.

But the move also exposes a familiar tension in Nostr development. The NIPs repository has a long-standing preference for “one way of doing things.” The NIP-CF discussion earlier this year made that explicit: every new feature “hurts interoperability” unless it’s actually necessary. By creating a parallel P2P standard instead of extending NIP-69, the proposal invites the same criticism. Why not fix NIP-69? The answer, according to the PR, is that NIP-69 is already deployed and its amt field is tied to satoshis. Changing it would break working software.

In my experience covering Nostr’s spec process, this is where the drama usually starts. Developers with production implementations tend to resist breaking changes; newcomers tend to argue that the old spec is too narrow. The new P2P NIP sits squarely in that fault line. It’s not a fork of the protocol, but it is a fork of the P2P standard, and it arrives with a commercial backer already using it. That combination, a new spec plus a live product, is exactly the kind of event that forces the community to confront its governance gaps. As we reported earlier this year in NostrMag , when a protocol has no formal governance model, decisions about which NIPs get merged and which maintainers hold sway “become intensely personal”.


The Case Against the New NIP

A second P2P standard fragments liquidity further, at least in the short term. Clients that already support NIP-69 must now choose whether to add kind 35353, and relay operators may see duplicate order books. If adoption stays confined to QvaPay and a handful of regional platforms, the NIP becomes a niche spec rather than a unifying layer. The absence of listed implementations beyond QvaPay at the time of writing is a yellow flag.


The Case for the New NIP

Stablecoin P2P trading is a massive, underserved market, and Nostr’s relay-agnostic design is a natural fit. The proposal’s strict number format, fixed-price and premium options, and signed trade history give builders a credible foundation for aggregation. If even a few additional platforms adopt the format, Nostr could become the neutral data layer for P2P markets that currently live in closed APIs and Telegram groups. The fact that QvaPay shipped before the NIP was merged suggests demand is real, not theoretical.


Summary

The new P2P NIP for non-Bitcoin assets is the most concrete Nostr development of the past seven days. It ships with a live implementation, targets a genuine market need, and forces a conversation about how Nostr balances interoperability with experimentation. I think it’s worth watching closely. The spec itself is still a draft, and the governance questions it raises are unresolved. But for developers building in the P2P space, it’s the first credible path to a shared order book that doesn’t require a centralized intermediary. The next few weeks will tell whether other platforms follow QvaPay’s lead or whether the proposal remains a single-platform experiment.

Comments