description hash
Am I understanding right that NIP57 requires the invoice description of the Zap invoice to be set to the Zap request?
Running into issues where the invoice description byte size is higher than the LND limit, so wondering if I'm reading the spec wrong. nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpremhxue69uhkvet9v3ejumn0wd68ytnzv9hxgtmsdac82mrpwgq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqrzexjn
Discussion
What about those parts, taken directly from the NIP:
"If the zap request is valid, the server should fetch a description hash invoice where the description is this zap request note and this note only. No additional lnurl metadata is included in the description."
"Zap receipts are only created when the invoice description (committed to the description hash) contains a zap request note."
"Parse the bolt11 description as a JSON nostr event. This SHOULD be validated based on the requirements in Appendix D, either when it is received, or before the invoice is paid."
I interpret them as referring to the description itself.