Nostr Zaps: Lightning Tipping Platforms and Clients Compared

Nostr Clients with Lightning Zap Support

Nostr zaps are Lightning Network payments attached to social events: notes, replies, profiles, and long-form content. Unlike tips on centralized platforms, zaps are peer-to-peer. No intermediary takes a cut, no platform can freeze your earnings, and the payment settles in seconds. The protocol specification (NIP-57) standardizes how clients request, send, and display these payments, creating an interoperable tipping layer across dozens of independent apps.

The Nostr ecosystem now spans over 140 clients and 850+ relays operating in more than 40 countries. Zap volume surged past 20 million zaps in a two-week window in early 2025, making social Lightning tipping one of the most active use cases on the Lightning Network. The following table compares the most widely used Nostr clients that support zapping.

Every client listed above is open source. This is a core principle of the Nostr ecosystem: users can verify that no client is surveilling their activity or intercepting their payments. For a broader look at how Lightning payments compare to on-chain Bitcoin transactions, see the Lightning vs on-chain comparison tool.

How NIP-57 Zaps Work

NIP-57 defines two event kinds that together form the zap protocol. Kind 9734 is a zap request: a signed event the payer's client constructs and sends to the recipient's LNURL pay endpoint. Kind 9735 is a zap receipt: a confirmation event the recipient's Lightning service publishes to Nostr relays after the invoice is paid.

The full flow works as follows:

1. The client fetches the recipient's LNURL pay endpoint and checks that the allowsNostr flag is set to true
2. The user taps the zap button. The client creates a signed kind 9734 event containing the recipient's pubkey (p tag), target relay list, amount in millisatoshis, and optionally the event ID being zapped (e tag)
3. The client sends this event via HTTP GET to the LNURL callback URL with amount, nostr, and lnurl query parameters
4. The recipient's Lightning service validates the request and returns a BOLT 11 invoice whose description hash commits to the zap request
5. The client pays the invoice through the user's connected Lightning wallet (via NWC, built-in wallet, or external app)
6. Upon payment confirmation, the Lightning service publishes a kind 9735 zap receipt to the relays specified in the original request
7. All clients subscribed to those relays see the zap receipt and display it on the relevant note or profile

Because the zap receipt includes the original Lightning invoice and the payment preimage, any client can independently verify that the zap actually occurred. This makes zap counts cryptographically verifiable, unlike like counts on traditional social platforms, which can be faked by the platform operator.

Nostr Wallet Connect (NIP-47)

Nostr Wallet Connect (NWC) is the protocol that bridges Nostr clients to Lightning wallets. Defined in NIP-47, it allows any client to send payment commands to a remote wallet without the user switching apps or copy-pasting invoices. The connection uses a nostr+walletconnect:// URI containing the wallet's public key, a client-specific secret key, and relay URLs.

NWC supports commands including pay_invoice, pay_keysend, make_invoice, get_balance, and list_transactions. Each connection uses unique keypairs, so payment activity from one client cannot be linked to the user's Nostr identity or to payments made from another client. Communication between client and wallet is encrypted using NIP-44 v2.

NWC is now supported by Primal, Damus, Amethyst, Iris, 0xchat, YakiHonne, Snort, Nostur, and Coracle. On the wallet side, services like Alby, Mutiny (before its shutdown), and other Lightning wallets offer NWC connection strings. This interoperability means users can pair any NWC-compatible wallet with any NWC-compatible client: the wallet choice and the client choice are fully independent.

Client-by-Client Breakdown

Primal

Primal is the most polished all-in-one Nostr client, available on iOS, Android, and the web. Its defining feature is the built-in Primal Wallet, which eliminates the biggest friction point in zapping: wallet setup. New users can start sending and receiving zaps immediately without configuring an external Lightning wallet or understanding Lightning addresses.

Primal v3.0 (released March 2026) added zap-based poll voting, NIP-46 remote login for signing into other Nostr clients securely, and NIP-50 full-text search across Nostr content. Its custom caching layer delivers near-instant feed loading, making it the smoothest experience for users coming from centralized social apps.

Damus

Damus was the first major Nostr client on iOS and played a pivotal role in popularizing zaps on mobile. In June 2023, Apple pressured Damus to remove post-level zaps from the App Store version, classifying them as "selling digital content" without using Apple's in-app purchase system. Damus negotiated a compromise: profile-level zaps (direct peer-to-peer transfers) remain, but zapping individual notes is restricted on the App Store build. Despite this limitation, Damus retains a loyal user base and has since added NWC integration for wallet connectivity.

Amethyst

Amethyst is the premier Nostr client for Android, with the broadest NIP implementation of any mobile client. Its zap UX is efficient: tapping the zap icon sends the default amount instantly, while long-pressing opens a menu with configurable preset amounts. Version 1.06.0 (March 2026) added comprehensive NIP-47 NWC wallet support, allowing users to pair any compatible Lightning wallet and pay natively without switching apps. Amethyst also supports keysend payments and advanced relay management.

Iris

Iris has the widest platform coverage of any Nostr client: iOS, Android, web, and desktop (Windows, macOS, Linux). It ships with a built-in Cashu ecash wallet, enabling instant zaps without external wallet configuration. The client is designed as an accessible entry point for users new to Nostr, with a familiar social media interface. Its offline-first architecture means it does not depend on any single centrally managed server.

Snort

Snort is a web-based Nostr client built with React. It provides a clean, fast interface for browsing Nostr content and sending zaps through connected NWC wallets. Snort operates a subscription model to fund development, separate from zap functionality. As a web app, it requires no installation and works across all desktop browsers.

Wallet Integration Comparison

How a client connects to a Lightning wallet determines the zap experience. There are three models in use across the ecosystem:

The trend across the ecosystem is clear: NWC has become the universal standard for wallet connectivity, with built-in wallets offered as a convenience layer for new users. For users who prioritize self-custody, pairing a client with an external Lightning wallet via NWC preserves full control over funds while still enabling one-tap zaps.

Nostr + Lightning as a Monetization Model

The combination of Nostr and Lightning represents a fundamentally different model for content monetization. On traditional platforms, creators earn through advertising revenue shares, which requires algorithmic optimization for engagement, platform lock-in, and acceptance of content moderation policies set by a single company. Nostr inverts this: creators publish to relays they choose, audiences find them through a decentralized discovery layer, and micropayments flow directly from reader to creator via Lightning.

This model eliminates the platform take rate entirely. On YouTube, creators receive roughly 55% of ad revenue. On Substack, the platform takes 10% of subscription revenue. On Nostr, 100% of every zap reaches the creator (minus routing fees, which are typically fractions of a cent). For a deeper analysis of how this compares to existing creator payment models, see our research on creator economy payments.

The model also changes incentive structures. Because zaps are voluntary and per-post, creators are rewarded for individual pieces of valuable content rather than for maximizing time-on-platform. There is no algorithm to game, no ad inventory to protect, and no content policy that can demonetize a creator overnight. The tradeoff is discoverability: without a centralized recommendation engine, creators must build audiences through organic sharing and relay presence.

The Nostr protocol's approach to identity and payments aligns with the broader shift toward decentralized infrastructure. For more context on how Nostr intersects with Bitcoin-native identity systems, see our research on Nostr, Bitcoin identity, and payments.

How to Choose a Nostr Client for Zapping

If you want the easiest onboarding with minimal setup: Primal. Its built-in wallet means you can start zapping within minutes of downloading the app. Available on iOS, Android, and web.

If you are on Android and want maximum protocol coverage: Amethyst. It implements the broadest set of NIPs and offers the most granular control over relay selection, zap amounts, and wallet configuration.

If you are on iOS and want a native experience: Damus for its established community and NWC support, or Nostur for a more mainstream-feeling interface. Note that both have Apple-imposed restrictions on post-level zaps.

If you prefer a web-based client with no installation: Snort for a focused social feed, or Iris for its broader feature set including encrypted messaging and ecash.

If privacy is your priority: clients with Cashu ecash wallets (Iris, 0xchat, YakiHonne) use blind signatures that prevent the mint from linking payments to your identity. Pairing any client with a self-custodial Lightning wallet via NWC also preserves payment privacy through the Lightning Network's onion routing.

Frequently Asked Questions

What are Nostr zaps?

Nostr zaps are Lightning Network payments attached to Nostr social events (notes, profiles, or long-form content). Defined by the NIP-57 specification, zaps allow users to send satoshis directly to content creators without any intermediary. Each zap produces a cryptographically verifiable receipt (kind 9735 event) published to Nostr relays, so zap counts cannot be faked by the platform.

How do I set up zapping on Nostr?

The fastest method is to download Primal (iOS, Android, or web) and use its built-in wallet. For other clients, you need a Lightning wallet that supports Nostr Wallet Connect (NWC). Set up the wallet, generate a connection string, and paste it into your Nostr client's wallet settings. You also need a Lightning address on your Nostr profile so others can zap you.

Why did Apple remove zaps from Damus?

Apple did not fully remove Damus, but in June 2023 it required Damus to remove post-level zaps from the App Store build. Apple classified zapping individual notes as "selling digital content," which under App Store guidelines requires using Apple's in-app purchase system (with its 30% commission). Damus negotiated to keep profile-level zaps (direct peer-to-peer transfers), which Apple accepted as person-to-person payments rather than content purchases.

What is Nostr Wallet Connect (NWC)?

Nostr Wallet Connect (NWC), defined in NIP-47, is a protocol that lets Nostr clients communicate with Lightning wallets remotely. It uses a nostr+walletconnect:// URI to establish an encrypted channel between client and wallet, enabling commands like pay_invoice and get_balance without app switching. Each connection uses unique keypairs, preventing payment activity from being linked to the user's Nostr identity.

Can I receive zaps without running a Lightning node?

Yes. Most users receive zaps through a custodial Lightning address provided by services like Alby, Wallet of Satoshi, or the built-in wallets in Primal and Iris. These services handle Lightning routing on your behalf. If you prefer self-custody, you can run your own Lightning node or use a service that provides an LNURL endpoint connected to your node.

How much do Nostr zaps cost in fees?

Lightning routing fees for zaps are typically fractions of a cent for small amounts (under 1,000 sats). The recipient receives the full zap amount minus routing fees, which usually total 0-3 satoshis for well-connected nodes. There is no platform commission: unlike traditional tipping platforms that take 20-30%, Nostr and Lightning impose no intermediary fee. The primary cost is the Lightning routing fee, which scales with the payment amount but remains negligible for typical zap sizes.

What is the difference between zaps and keysend payments?

Zaps (NIP-57) are invoice-based payments that produce a public, verifiable receipt on Nostr relays. They require the recipient to have an LNURL endpoint that supports Nostr zaps. Keysend payments are spontaneous Lightning payments sent directly to a node's public key without an invoice. Keysend is simpler but does not produce a Nostr-visible receipt, so the payment will not appear as a zap on the recipient's notes. Some clients support both methods.

Are Nostr zaps private?

Zap receipts (kind 9735 events) are published to Nostr relays and are publicly visible by default, including the sender's pubkey and the amount. NIP-57 supports anonymous zaps by omitting the sender's identity from the receipt, though not all clients implement this option. The Lightning payment itself benefits from onion routing, which obscures the payment path from intermediary nodes. For maximum privacy, users can combine anonymous zaps with Cashu ecash wallets, which use blind signatures to unlink the minting and spending of tokens.

Note: Nostr zap infrastructure depends on LNURL services that may be custodial. When evaluating clients, consider whether the wallet integration preserves self-custody or introduces a trusted third party. Layer 2 solutions like Spark are extending Bitcoin's payment capabilities with instant, low-cost transfers that complement the Lightning tipping ecosystem.

This tool is for informational purposes only and does not constitute financial advice. Client features, wallet integrations, and protocol specifications change frequently. Data is based on publicly available information as of mid-2026. Always verify current client capabilities and wallet custody models before sending or receiving payments.