Bitcoin zaps in chat
Obelisk lets you send Bitcoin over Lightning directly from a chat message using NIP-57 zaps, paid by a wallet you connect with Nostr Wallet Connect (NIP-47) or by a WebLN browser extension. No custodian, no platform fee, no middleman. Just your wallet, the recipient's wallet, and a signed Nostr event.
What is a zap, really?
A zap is a Lightning payment that's also a public Nostr event. You pay sats to someone over Lightning, and the receipt (a signed kind 9735 event) is published to the relay so everyone in the conversation sees that the sats moved.
In Obelisk, a zap is just a button on a message. Click it, pick an amount, your wallet pays the invoice, the recipient's wallet receives, and the chat shows the zap inline.
What's involved
- NIP-57 defines the zap request and receipt events and the LNURL flow that turns a Nostr identity into a Lightning invoice.
- Your wallet pays that invoice, in one of two ways:
- a wallet you connect with Nostr Wallet Connect (NWC, NIP-47): Obelisk sends the payment request to your wallet over a Nostr relay;
- a WebLN browser extension such as Alby: Obelisk hands it the invoice inside the browser.
Either way, Obelisk sends sats from your wallet to anyone with a lud16 (Lightning address) in their Nostr profile, and never touches the funds or your wallet's keys.
How it works in the app
- Set up a wallet. Either open Settings > Wallet (on the phone, Preferences) and paste the Nostr Wallet Connect link from your wallet's app (Alby Hub, for example), or install a WebLN extension such as Alby. If you have both, the connected wallet pays. The zap window says which one will.
- Pick a message. Click the zap button on a chat message.
- Pick an amount. Choose a quick amount (21 to 21,000 sats) or type your own.
- Sign and pay. Obelisk builds a
kind 9734zap request, signs it with your Nostr key, sends it to the recipient's LNURL endpoint to get a Lightning invoice, and asks your wallet to pay it. - The zap appears. Obelisk posts a ⚡ reaction carrying the invoice to the channel, and the recipient's LNURL endpoint publishes a
kind 9735zap receipt. The chat shows the zap.

What's private and what isn't
- The amount and recipient are public. Anyone reading the channel can see "Alice zapped Bob 1000 sats."
- Your wallet's balance is private. Obelisk never asks for it, or for your history.
- Your wallet keys are private. They never leave your wallet. Over NWC, Obelisk asks the wallet to pay invoices and, when the connection allows it, for its name and spending limit, so Settings can show them. The wallet enforces the limit you set there.
- The connection link stays on this device. The NWC link can spend from your wallet, so Obelisk seals it with a key your browser keeps, for your account only, and never stores it in the clear. Disconnecting or logging out deletes it. If the browser cannot keep that key, the wallet stays connected only until you close or reload the page.
- The Lightning routing is private the same way any Lightning payment is: onion-routed, no on-chain footprint.
What does it cost?
- No platform fee. Obelisk takes nothing. There is no platform.
- Lightning routing fees. A few sats at most for typical amounts.
- Wallet fees. Whatever your wallet provider charges, if anything.
Why this matters
Zapping turns "real money" into a primitive of group chat. Tip a great post. Pay a bounty. Crowdfund a project. Run a paid Q&A. None of it requires a payment processor, a credit card, or a middleman who can freeze the transaction.