Cowrie Research

nostr-wallet-auth-primary-sources-2026-05-03

3 min read

Nostr Wallet Auth (NWA) primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone NWA whitepaper or litepaper surfaced.
  • No merged canonical NIP for NWA was found in this pass; the clearest status signal was an unmerged draft entry in the public NIP index.
  • The clearest current source of truth is Alby’s NWC/NWA SDK documentation, the broader NWC ecosystem materials, the NIP index, and early first-party implementation notes from Mutiny.

Primary-source snapshots

1) Alby NWC JS SDK guide

2) Raw Alby SDK documentation

  • URL: https://raw.githubusercontent.com/getAlby/js-sdk/master/docs/nwc.md
  • Key excerpt:
    • The raw markdown repeats the same NWA description and keeps it adjacent to the broader NWC documentation, which makes its layered relationship explicit.
    • The examples show NWAClient generating a connectionUri for apps and parseWalletAuthUrl for wallets.
    • The docs say the example wallet implementation creates the final connection through the create_connection NWC command, confirming NWA is a bootstrap layer on top of NWC.

3) NWC homepage

  • URL: https://nwc.dev/
  • Key excerpt:
    • The homepage describes NWC as “an open protocol to connect lightning wallets to apps.”
    • It says apps can orchestrate payments without touching funds and highlights sustained app-wallet interaction over Nostr relays.
    • This is useful context because NWA makes the most sense as connection-bootstrap infrastructure inside the wider NWC model rather than as a standalone payment protocol.

4) awesome-nwc repository

  • URL: https://raw.githubusercontent.com/getAlby/awesome-nwc/master/README.md
  • Key excerpt:
    • The repository frames NWC as an open protocol implemented by Bitcoin Lightning wallets and apps.
    • It emphasizes that users connect wallets instantly and that apps orchestrate payments without ever touching funds.
    • The broader ecosystem inventory is useful evidence that NWA emerged to improve a real, already-populated interoperability surface rather than a toy demo stack.

5) Mutiny launch post

  • URL: https://blog.mutinywallet.com/nostr-wallet-auth/
  • Key excerpt:
    • Mutiny says NWA is a protocol built on top of NWC where the client or service generates the request and the wallet and service negotiate the secret in the background.
    • The post describes one-click or QR-based connection setup and emphasizes that the wallet remains in charge of approvals and revocation.
    • It also says early support at the time was live in Mutiny and Zapple Pay, which is helpful evidence of real implementation-driven origins.

6) Public NIP index status page

  • URL: https://codeberg.org/nostr/nip-index
  • Key excerpt:
    • The index lists “uNIP-49: Nostr Wallet Auth” as an unmerged draft.
    • That status matters because it distinguishes NWA from finalized NIPs and explains why current ecosystem docs are clearer operational sources than a merged canonical NIP text.

7) Proposed NIP pull request

  • URL: https://github.com/nostr-protocol/nips/pull/851
  • Key excerpt:
    • Mutiny’s post points to this pull request as the draft standards discussion for NWA.
    • Even without treating the PR as finalized specification, it is a useful anchor showing that NWA has explicit standardization intent rather than being only one wallet’s proprietary pairing flow.

Working conclusion

Nostr Wallet Auth is best cataloged as wallet-connectivity bootstrap infrastructure. The deciding evidence in this pass was the repeated description of app-generated connection requests, client-generated secrets, wallet approval of the initial pairing, and explicit dependence on NWC for the resulting long-lived wallet-app relationship, combined with the important caveat that the standardization status still appears draft and unmerged.

Graph View