Nostr Wallet Connect

• Name: Nostr Wallet Connect (NWC)
• URL: https://nwc.dev/
• Category: wallet-connectivity protocol / remote Lightning wallet access standard / Nostr-based payment-intent rail
• Tags: bitcoin-ecosystem nostr-ecosystem
• Summary: Nostr Wallet Connect is a Nostr-based wallet-connectivity rail for Lightning apps, not a wallet and not a payment processor. The useful point is the delegated session: apps get a reusable way to request payments and receive wallet events over relays without taking custody.
• What it does:
  • Defines a standard connection URI and request-response pattern for apps to talk to remote Lightning wallets
  • Uses Nostr relays as the transport layer for encrypted wallet requests, responses, and notifications
  • Lets apps initiate repeated wallet actions after a one-time wallet connection, without needing custody of user funds
  • Supports connection flows suited to both publicly reachable wallets and mobile or self-hosted wallets
  • Publishes SDK and integration tooling across multiple languages and platforms, plus web-connection tooling like Bitcoin Connect
  • Gives wallets a standardized way to advertise supported capabilities and notifications to compatible apps
• Key claims:
  • The main site describes NWC as “an open protocol to connect bitcoin wallets to apps” and emphasizes one-click, non-custodial in-app payments with no Nostr account required for end users
  • The docs landing page frames NWC as “One Open Protocol to Connect Bitcoin Wallets and Apps,” explicitly targeting both wallet developers and app or website developers
  • The docs’ ?ask= query flow says NWC standardizes how apps and wallets exchange payment intents rather than the underlying payment network, which is a strong clue that this belongs in interoperability infrastructure rather than wallet or payments-app categories
  • The docs also explain that apps and wallets can communicate through Nostr relays, with one-time connection setup via QR code, deeplink, or manual configuration, and support both HTTP and Nostr connection flows depending on the wallet environment
  • NIP-47 defines the client, user, and wallet-service roles; specifies encrypted request, response, and notification events over relays; and recommends unique keys per connection to avoid linking payment activity to the user identity key
  • The site and docs highlight a real developer tooling layer, including JavaScript, React Native, Rust, Dart, Flutter, and Python SDKs, plus Bitcoin Connect, an Alby developer sandbox, and an NWC faucet
  • The homepage’s app gallery and wallet list show the protocol is already used as a shared interface across multiple Bitcoin and Nostr applications rather than a one-off demo standard
• Whitepaper: No canonical standalone NWC whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs plus the NIP-47 specification and related SDK/tooling pages; see ../whitepapers/nostr-wallet-connect-primary-sources-2026-04-30.md.
• Sources:
  • https://nwc.dev/
  • https://docs.nwc.dev/
  • https://docs.nwc.dev/introduction/welcome-to-nwc.md?ask=What%20does%20NWC%20actually%20standardize%2C%20how%20do%20apps%20and%20wallets%20communicate%2C%20and%20what%20developer%20tools%20or%20SDKs%20does%20the%20documentation%20highlight%3F
  • https://github.com/nostr-protocol/nips/blob/master/47.md
  • https://github.com/getAlby/js-sdk
  • https://bitcoin-connect.com/

Internal linkages

• Best adjacent reads: webln, clink, and lnurl.

Control surface

• The real leverage sits in relay choice, per-connection secrets, capability scoping, and which wallet implementation apps normalize as the default NWC path.

• Last reviewed: 2026-05-27 UTC