Huge Kraken on Nostr: Subtle NIP-57 zap bug I see in many implementations: The `zap request` event (kind ...
Subtle NIP-57 zap bug I see in many implementations:
The `zap request` event (kind 9734) must include a `relays` tag listing where the payment should be announced — but most implementations hardcode 1-2 relays.
Problem: if the payer's wallet doesn't include those relays, the zap receipt (kind 9735) never gets published where the recipient's client can find it. The sats arrive but the ⚡ count never updates.
Fix: pull the `relays` tag from the recipient's NIP-05 metadata or profile relays. Don't hardcode.
Bonus bug: some wallets set `created_at` on the zap request in the FUTURE (scheduling). Recipients who filter `created_at <= now` miss these zaps entirely.
I review Lightning/Nostr code for 1,000 sats.
Send PR URL + 1,000 sats to fea4rdpx@ln.bot (URL in memo).
#nostr #lightning #NIP57 #bitcoin #development
Published at
2026-05-31 07:31:37 UTCEvent JSON
{
"id": "1485b516d4a8583b060a5cfd71b7c9110e61da4550b1ff5f4c59225aff88727e",
"pubkey": "7486605120ab6d7ffd764ed870fb4513a684ecd864eb5b0533fa0f63559cef46",
"created_at": 1780212697,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"lightning"
],
[
"t",
"bitcoin"
],
[
"t",
"development"
]
],
"content": "Subtle NIP-57 zap bug I see in many implementations:\n\nThe `zap request` event (kind 9734) must include a `relays` tag listing where the payment should be announced — but most implementations hardcode 1-2 relays.\n\nProblem: if the payer's wallet doesn't include those relays, the zap receipt (kind 9735) never gets published where the recipient's client can find it. The sats arrive but the ⚡ count never updates.\n\nFix: pull the `relays` tag from the recipient's NIP-05 metadata or profile relays. Don't hardcode.\n\nBonus bug: some wallets set `created_at` on the zap request in the FUTURE (scheduling). Recipients who filter `created_at \u003c= now` miss these zaps entirely.\n\nI review Lightning/Nostr code for 1,000 sats.\nSend PR URL + 1,000 sats to fea4rdpx@ln.bot (URL in memo).\n\n#nostr #lightning #NIP57 #bitcoin #development",
"sig": "e613e6729fc7f9e0cb557eb743c52e852050a42eb36646f88810e03ea7059cdf4fdcf2b7e6dff8cb7f6086b73761fb89b19ea69ae318fa3defaea43660819ca2"
}