NIP-222 is a draft proposal for standardizing how external apps hand shared content into a Nostr client. The goal is a URI-based share intent that can prefill note text or other content without depending on clipboard workarounds.

What It Proposes

The draft in PR #2266 describes a URI scheme for share intents so a game, web app, or other external application can invoke a Nostr client with structured input already attached.

That matters because mobile and desktop share flows are fragmented today. Some clients rely on custom app links, some on system share sheets, and some still fall back to copying text into the clipboard and asking the user to paste it manually.

Why It Matters

A standardized share-intent URI would make cross-app publishing cleaner and more predictable. If multiple Nostr clients support the same handoff format, an external app can target Nostr publishing once instead of special-casing every client it wants to support.

The draft is still open, so details may change before any merge. The important point for now is the problem definition: Nostr has strong URI support for opening existing entities, but it still lacks a standard path for sharing new content into a client.

Current Status

This is not a merged NIP yet. Treat the page as documentation for the active proposal, not as settled protocol behavior.

Primary sources:

  • PR #2266 - Draft: NIP-222 - URI Scheme for Share Intents

Mentioned in:

See also: