Zap

A Zap is a Bitcoin micropayment sent across the Nostr network using the Lightning Network. Where a conventional social platform offers a "like" that costs nothing and means little, a Zap moves real satoshis from one person to another and attaches a public, verifiable receipt to the note being tipped. Defined by NIP-57, it ties Nostr's signed-message layer to Bitcoin's payment layer — value transfer as a native feature of the protocol rather than a bolted-on tip jar.

How a Zap works

The flow has three moving parts. First, your client builds a zap request — a signed Nostr event naming the recipient, the note being zapped, and the amount — and sends it to the recipient's Lightning service. That service returns a Lightning invoice, which your wallet pays over the Lightning Network. Once payment settles, the service publishes a zap receipt — another signed Nostr event — to the recipient's relays, and clients everywhere can display the tip alongside the note. The recipient needs a Lightning address or LNURL endpoint in their profile, which can be self-hosted or provided by a custodial wallet. Because settlement rides on Lightning, it is fast, final, and denominated in bitcoin rather than platform points.

The custody spectrum

Zaps inherit whatever custody model the endpoints use, and it is worth being honest about the defaults. Most casual zapping today flows through custodial Lightning wallets, because a receipt-publishing, always-on Lightning endpoint is exactly the kind of infrastructure a phone cannot provide alone. That is a reasonable on-ramp for pocket change, but it means a third party holds the sats and sees the traffic. The sovereign endgame is running your own node with well-managed channels and inbound liquidity, plus a self-hosted Lightning address endpoint — at which point tips land directly in channels you control, with no custodian able to freeze, skim, or surveil them. As with everything in this stack, custody is a dial, not a switch, and you can move it toward yourself over time.

Why it matters

Zaps demonstrate native, permissionless monetization without an advertising middleman, payment processor, or platform cut. A writer, developer, or educator can be paid by a global audience in seconds, with no account to ban and no payout threshold to reach. The signal quality is also different in kind: a zap is costly, so a heavily-zapped note carries proof-of-value that an army of bots cannot fake for free. For sovereign Bitcoiners the loop closes neatly — speech published through relays you choose, identity held as a keypair under self-custody, and money moving on a censorship-resistant network. See D-Central's digital sovereignty hub for combining Lightning and self-hosted communications into one stack.

Zaps in practice

Culturally, zaps behave less like payments and more like weighted applause. Most are small — a few sats to a few thousand — sent in volume, and clients surface totals and top zappers on each note, so the sats function as a public, costly signal of what an audience actually values. Senders can attach a comment that rides along with the receipt, keep their identity on the receipt, or zap anonymously; recipients simply watch value accumulate with no invoicing, no follow-up, no platform statement. For creators the operational questions are mundane and important: a custodial Lightning address gets you receiving in minutes, while a self-hosted endpoint needs an always-on node and a public web service that can issue invoices on demand. Many start custodial and graduate — the protocol does not care, and the notes, the audience, and the identity keys all come along unchanged when you move. That painless exit is the quiet leverage of the whole design: a custodian that misbehaves loses only your custody, never your identity or your following.