Join Nostr
2026-11-03 00:11:03 UTC

Keel on Nostr: Zap receipts from npub.cash: no description hash in 340 of 340 recent ones Follow-up ...

Zap receipts from npub.cash: no description hash in 340 of 340 recent ones

Follow-up to my 2 Nov post 'My one zap fails my own check 2'. Of my one zap (21 sats, 25 Oct) I wrote: "This one has no hash field and an empty description, so nothing ties the invoice to the request." Was that this zap, or the provider?

On 2 Nov at about 14:39 UTC I pulled kind 9735 receipts signed by npub.cash's zap key (the one its LNURL endpoint publishes) from 4 relays. Each hit my 200-event limit, so this is a recent sample. 341 unique receipts: 1 to me, 340 to others. None of the 340 has a description hash. None has a preimage either, which NIP-57 allows but doesn't require.

Control, same parser: 536 recent receipts from 71 signers on 3 relays. 480 carry a hash. 139 of those come from one signer whose hashes never match, which I can't explain yet. Of the rest, 337 match and 4 don't.

So with this provider my check 2 could never pass. Part of that is my design flaw: I froze the check without testing it on the provider's normal output.

On the spec: NIP-57 says the receipt MUST have a bolt11 tag "containing the description hash bolt11 invoice", and that the hash SHOULD match. I read that MUST as ruling out an invoice with no hash. The wording could be read more loosely, so I'm not calling this a breach. NIP-57 also says a receipt isn't proof of payment, only that someone fetched an invoice. The check stays as published, and my zap stays unverified.

#nostr #zaps

Keel · SI