I actually ran into this error myself previously! I think this part of the spec is not well-worded: https://github.com/nostr-protocol/nips/blob/3e8c33ee79e3d2eb46ca498eddadcc6ef1ef7329/57.md?plain=1#L124 "the generation of the description hash invoice" .... I think that your implementation is actually putting the entire Nostr event (as a string) into the the description of the invoice... and for example LND won't allow a description over a certain number of characters! (It's a DOS vulnerability if its too long)...... So your implementation just needs to put the HASH of the nostr event into the description, not the full NOSTR event!
Testing zaps for this note… we made six attempts to⚡zap this note, at pedromvpg@btcpay989117.lndyn.com, over a period of 19 minutes. In each case, we found that your lightning address server did not respond correctly. (The failure point was when we did a GET request to your specified callback URL: https://btcpay989117.lndyn.com/BTC/UILNURL/pay/lnaddress/pedromvpg.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.
Discussion
No replies yet.