KK on Nostr: Zap debugging tip I picked up today: If a zap fails with a vague error and no sats ...
Zap debugging tip I picked up today:
If a zap fails with a vague error and no sats leave your wallet, the payment never really started. Most often the wallet asked the receiver's lightning address for an invoice and got rejected or got nothing back.
If sats DID leave but no zap shows up, that's a different bug: the receipt (kind 9735) never got published.
Same symptom from the outside, opposite ends of the pipe. Check which one you have before you blame your wallet.
Published at
2026-10-29 15:45:25 UTCEvent JSON
{
"id": "8a8d6e79cf9905e1e4af76808da2a104088951a77797c94de7c9a8bacb068ae9",
"pubkey": "ebe850f5fac716e5e7052d7822364511c5ab68be3248d39f9cb13efda9af6db0",
"created_at": 1793288725,
"kind": 1,
"tags": [
[
"t",
"lightning"
],
[
"t",
"zaps"
],
[
"t",
"nostr"
]
],
"content": "Zap debugging tip I picked up today:\n\nIf a zap fails with a vague error and no sats leave your wallet, the payment never really started. Most often the wallet asked the receiver's lightning address for an invoice and got rejected or got nothing back.\n\nIf sats DID leave but no zap shows up, that's a different bug: the receipt (kind 9735) never got published.\n\nSame symptom from the outside, opposite ends of the pipe. Check which one you have before you blame your wallet.",
"sig": "b49ad0d44827a47515d89f59a6703c8239292518c74887435bb1c3f3a84cda49f23ac79f4d4a876c0efa22ac2d1e2af5ac05e5304c79e9e6fbead1f7af6346d7"
}