NWC Wallet Comparison: Nostr Wallet Connect Implementations
Compare Nostr Wallet Connect implementations across wallets for remote signing, zap support, spending limits, and payment automation via NIP-47.
Nostr Wallet Connect Implementations Compared
Nostr Wallet Connect (NWC) is a protocol defined in NIP-47 that lets any application send Lightning payment requests to a user's wallet through Nostr relays. Instead of each app building its own wallet, NWC separates the app from the wallet: the user pairs once, sets a budget, and every compatible app can pay through that single connection. The protocol has been described as the "USB-C connector" of Bitcoin wallets.
The following table compares the major wallets that act as NWC service providers: the backend that actually holds funds and executes payments when an app sends a request.
| Wallet | Custody Model | Backend | NWC Role | Spending Limits | Platform |
|---|---|---|---|---|---|
| Alby Hub | Self-custodial | LND, LDK, Greenlight | Service + Client | Per-app budget, expiry | Web (self-hosted), Cloud |
| Zeus (v0.12+) | Self-custodial | Embedded LND, LDK, CLN REST | Service + Client | Per-connection budget, expiry | iOS, Android |
| LNbits | Self-hosted | Any LNbits funding source | Service | Per-wallet permissions, expiry | Web (self-hosted) |
| Coinos | Custodial | Coinos server | Service | Budget, routing fee cap, renewal | Web |
| Primal Wallet | Custodial | Strike (Zap Solutions) | Service | App-level budget | iOS, Android, Web |
| Cashu.me | Ecash (mint-custodied) | Cashu mint | Service | Satoshi spending allowance | Web |
| Minibits | Ecash (mint-custodied) | Cashu mint | Service | Configurable | Android |
Mutiny Wallet previously supported NWC but shut down its hosted service at the end of 2024. The code remains open source, though the app was removed from app stores. Phoenixd (ACINQ's server daemon) does not support NWC natively but can be bridged through LNbits or Alby Hub.
How the NWC Protocol Works
NWC uses three Nostr event kinds to coordinate payments between an app (the client) and a wallet (the service). All payment data is end-to-end encrypted using NIP-04 or the newer NIP-44 encryption, so the relay carrying the messages cannot read payment details.
- Kind 13194: the info event. The wallet service publishes this replaceable event to advertise which NIP-47 methods it supports, as a space-separated plaintext string.
- Kind 23194: the request event. The app sends an encrypted request (such as
pay_invoice) to the wallet service. - Kind 23195: the response event. The wallet service returns the encrypted result (success or error) to the app.
The connection is established through a URI that contains the wallet service's public key, a shared secret, and the relay URL. This URI is effectively a credential: anyone who possesses it can send payment requests to the wallet within the configured limits. Each app connection gets its own unique secret, so revoking one app does not affect others.
For a deeper explanation of the protocol flow and its implications for keysend and automated payments, see our research article on NWC remote signing.
NIP-47 Method Support by Wallet
NIP-47 defines a core set of methods that wallets can implement. Not every wallet supports every method. The kind 13194 info event advertises which methods are available, so apps can adapt their UI accordingly. The following table shows method support across major NWC wallet services based on published documentation and community reports.
| Method | Alby Hub | Zeus | LNbits | Coinos | Primal | Cashu.me |
|---|---|---|---|---|---|---|
pay_invoice | Yes | Yes | Yes | Yes | Yes | Yes |
make_invoice | Yes | Yes | Yes | Yes | Yes | Limited |
get_balance | Yes | Yes | Yes | Yes | Yes | Yes |
get_info | Yes | Yes | Yes | Varies | Varies | Varies |
lookup_invoice | Yes | Yes | Yes | Varies | Varies | No |
list_transactions | Yes | Yes | Yes | No | No | No |
pay_keysend | Yes | Yes | Yes | Partial | No | No |
multi_pay_invoice | No | No | No | No | No | No |
Alby Hub has the most complete method coverage, followed by Zeus and LNbits. The multi_pay_invoice method, which would allow batch payments in a single request, is defined in the spec but not yet widely implemented. Coinos has reported issues with pay_keysend, which can cause boost payments in podcast apps to fail. Method support changes with each release, so check the wallet's kind 13194 event or documentation for the current list.
App Compatibility
NWC separates wallets from apps. Any app that implements the NWC client protocol can connect to any wallet that runs the NWC service. In practice, compatibility depends on which methods the app calls and whether the wallet supports them. The primary use case is zaps: sending Lightning tips on Nostr content. The following apps support NWC connections to external wallets.
- Damus (iOS): NWC for zaps, connects to any NWC wallet service
- Amethyst (Android): NWC for zaps and payments
- Primal (iOS, Android, Web): built-in wallet with NWC, also accepts external NWC connections
- noStrudel (Web): full NWC support for zaps and Lightning payments
- Coracle (Web): NWC client for zaps
- Snort (Web): NWC client for zaps
- Habla News (Web): NWC for zapping long-form content
- Stacker News (Web): NWC for zaps, boosts, and tipping
- Wavlake (Web/Mobile): NWC for streaming sats to music creators
These apps call pay_invoice at minimum and may also use get_balance to display wallet balance in the UI. Any NWC wallet service that supports these two methods will work with the apps listed above. For a broader comparison of Lightning-enabled apps, see our Lightning wallet comparison.
NWC vs LNURL
NWC and LNURL both simplify Lightning payments, but they solve different problems and use different transport layers. Understanding the distinction helps developers choose the right protocol for their use case.
| Dimension | NWC (NIP-47) | LNURL |
|---|---|---|
| Transport | Nostr relays (WebSocket) | HTTPS endpoints |
| Purpose | Remote wallet control | Payment request/response |
| Authentication | Nostr keypairs + shared secret | Varies (LNURL-auth uses signing) |
| Infrastructure | No web server needed (relay-based) | Requires HTTPS server, domain, TLS cert |
| Connection Model | Persistent, budget-scoped | Stateless per-request |
| Automation | Supports automated payments within limits | Requires user confirmation per payment |
| Scope | Pay, receive, query balance, list history | Pay, withdraw, auth, channel requests |
| Adoption | Growing: Nostr ecosystem, 350K+ users | Established: widely supported across wallets |
NWC's key advantage is eliminating the need for a web server. Any developer who can connect to a Nostr relay can add wallet functionality to their app. LNURL remains more broadly adopted outside the Nostr ecosystem and is better suited for one-off payment flows like point-of-sale or withdrawal links. For payment address standards, see our comparison of BIP-353 vs LNURL payment addresses.
Security Model and Spending Limits
NWC's security relies on the wallet service, not the app. The app never touches private keys or channel state. It can only request operations that the wallet has authorized for that specific connection. This design means a compromised app can only spend up to the budget the user configured, not drain the entire wallet.
Security controls available in most NWC wallet services:
- Per-app spending limits (maximum per transaction, daily or monthly caps)
- Connection expiry dates that force re-authorization
- Method-level permissions (allow pay but not receive, or vice versa)
- Independent revocation per connection without affecting other apps
- Custom relay selection to reduce exposure to untrusted infrastructure
The connection URI itself is the sensitive credential. It contains the wallet's public key, the shared secret, and the relay URL. Users should treat it like a password: do not paste it into untrusted apps, and revoke connections that are no longer needed. The relay can see event metadata (kinds and tags) but cannot decrypt the encrypted payload, so payment amounts and invoice details remain private between the app and the wallet.
Latency is a practical consideration. Nostr relay round trips typically add 1 to 5 seconds of delay compared to direct WebLN connections. For most zap and tipping use cases this is acceptable, but for latency-sensitive applications like point-of-sale terminals, the delay may matter. Self-hosted relays or low-latency public relays can reduce this overhead.
Self-Custodial NWC Options
NWC works with both custodial and self-custodial wallets. For users who want full control of their funds while using NWC for remote payments, three options stand out.
Alby Hub is the most mature self-custodial NWC service. It runs as a self-hosted application backed by LND, LDK, or Greenlight, with a web dashboard for managing app connections. Alby also offers a cloud-hosted option for users who want self-custody without managing infrastructure. It supports the broadest set of NIP-47 methods and has the largest developer ecosystem, including an SDK for JavaScript and integration guides for app developers.
Zeus (v0.12.0 and later) runs NWC as a service directly from a mobile phone using an embedded LND or LDK node. On Android, the service persists in the background. On iOS, a handoff mechanism handles incoming requests when the app is not in the foreground. Zeus supports per-connection budgets, expiry dates, method-level permissions, and custom relays.
LNbits provides NWC through its NWC Service Provider extension. Because LNbits supports multiple funding sources (LND, CLN, phoenixd, and others), it can serve as an NWC bridge for wallets that do not natively speak NIP-47. The extension requires a Nostr relay: either a third-party relay or the LNbits Nostrclient extension on a publicly reachable instance.
Ecash Wallets and NWC
Cashu-based ecash wallets have adopted NWC as an interface layer, letting users zap from ecash balances without switching apps. Cashu.me added NWC remote control in its v0.1 release with configurable spending allowances. Minibits on Android also supports NWC and has been reported as one of the more reliable ecash wallets for use with Nostr clients like Amethyst.
Ecash wallets are custodial by nature: the mint holds the underlying Lightning balance. The tradeoff is privacy. Cashu mints use blind signatures, so the mint cannot link individual payments to specific users. NWC adds a layer on top: the app sends a pay_invoice request to the ecash wallet, which redeems tokens at the mint and routes the Lightning payment. For more on ecash trade-offs, see our research on Chaumian ecash mints.
NWC and Payment Automation
NWC's budget-scoped connections make it suitable for automated payment workflows. A podcast app can stream sats to creators without requiring user confirmation for each micropayment. A Nostr client can auto-zap posts from followed accounts up to a daily limit. A merchant dashboard can generate invoices via make_invoice and monitor incoming payments via lookup_invoice.
These workflows complement Lightning infrastructure like Spark, which provides instant finality and VTXO-based payment management on Bitcoin. A wallet connected to Spark could expose NWC as an interface layer, letting any Nostr app trigger payments that settle on Bitcoin's base layer without requiring the app developer to integrate Lightning directly.
For developers building payment automation, the key constraint is method support. The wallet must implement pay_invoice for outbound payments and make_invoice for inbound. Alby Hub's JavaScript SDK wraps these methods in a WebLN-compatible interface, reducing integration effort for web apps. For more on Lightning payment integration patterns, see our research on Bitcoin payment automation.
Frequently Asked Questions
Can NWC work with self-custodial wallets?
Yes. Alby Hub, Zeus (v0.12+), and LNbits all support NWC in a self-custodial configuration where the user controls their own Lightning node. Alby Hub runs on LND, LDK, or Greenlight. Zeus uses an embedded node on mobile. LNbits acts as a bridge that can connect to any Lightning backend. In all cases, the user's private keys and channel state remain under their control, and the NWC protocol only handles payment requests within configured spending limits.
Is NWC secure enough for automated payments?
NWC is designed for automated payments within controlled limits. The security model relies on per-connection spending caps enforced by the wallet, not the app. A compromised app can only spend up to the budget the user set for that connection. All payment data is end-to-end encrypted between the app and wallet, so the relay cannot read payment details. For high-value automation, use a self-custodial wallet with low per-transaction limits and short connection expiry periods.
What is the difference between NWC and LNURL?
NWC is a remote wallet control protocol that runs over Nostr relays and maintains persistent, budget-scoped connections. LNURL is a set of HTTP-based payment request standards (pay, withdraw, auth, channel) that are stateless and require a web server. NWC enables automated payments without user confirmation (up to the configured budget), while LNURL typically requires user approval per transaction. NWC requires no web server infrastructure, only a Nostr relay connection.
Which wallets support NWC as a service provider?
As of late 2026, the main NWC wallet services are Alby Hub (self-custodial), Zeus (self-custodial mobile), LNbits (self-hosted), Coinos (custodial), Primal Wallet (custodial), Cashu.me (ecash), and Minibits (ecash). Mutiny Wallet previously supported NWC but shut down in December 2024. Phoenixd does not support NWC natively but can be bridged through LNbits or Alby Hub.
How do I connect a Nostr app to my Lightning wallet via NWC?
In your wallet's NWC settings, create a new app connection with a name, spending budget, and expiry date. The wallet generates a connection URI (starting with nostr+walletconnect://). Copy this URI or scan its QR code in the Nostr app's wallet settings. The app will confirm the connection and can then send payments through your wallet within the configured limits. Each app gets its own independent connection that can be revoked without affecting others.
Does NWC work without running a Lightning node?
Yes. Custodial NWC wallet services like Coinos and Primal Wallet handle the Lightning routing on their servers. Users connect to these services via NWC without running any node infrastructure. Ecash wallets like Cashu.me also work without a user-run node: the Cashu mint handles Lightning payments on behalf of the user. The tradeoff is custody: a third party holds the funds.
Can I use NWC to receive payments, not just send?
NWC supports receiving through the make_invoice method, which lets an app request the wallet to generate a Lightning invoice. Not all wallet services implement this method, and some ecash wallets support send-only NWC connections. Check the wallet's kind 13194 info event to confirm which methods are available before building receive flows.
This tool is for informational purposes only and does not constitute financial advice. NWC wallet support and method coverage change with each release. Data is based on publicly available documentation and community reports as of late 2026. Always check the wallet's official documentation or its kind 13194 info event for the current list of supported methods before relying on specific functionality.
Build with Spark
Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.
Read the docs →
