hampus on Nostr: It’s simply not compatible. NIP57 zap mandates that the description hash of the ...
It’s simply not compatible.
NIP57 zap mandates that the description hash of the invoice has to be the zap request note, whereas conventional with LNURL-pay invoices, it’s the LNURL-pay metadata that should be the desc hash.
So basically a zap is not really using LNURL-pay, it’s just the same URL endpoint.
So now all LNURL-pay servers has to also support this new propertary protocol.
If we’re going to think long-term, this can have some seriously bad implications, as both LNURL-pay and NIP57 progresses and moves forward.
But I can give you a clear-cut example: LUD-18 (
https://github.com/lnurl/luds/blob/luds/18.md) also let’s you commit arbitrary payer identities to a payment (which is the primary goal of NIP57).
But seeing how NIP57 takes precedence, there’s no way to use NIP57 and LUD-18 at the same time, which is just sad.
To make things in the right way, zaps should’ve just used the already specified and established way to commit data, which is LUD-18.
Published at
2023-03-23 07:01:03Event JSON
{
"id": "1c5fd708bc06ae12e637c52bdbd059fe2e5703767c51c2561cb4d0ae91ab9b8e",
"pubkey": "65594f279a789982b55c02a38c92a99b986f891d2814c5f553d1bbfe3e23853d",
"created_at": 1679554863,
"kind": 1,
"tags": [
[
"e",
"772fd838552b963cca238a000e5cb3e68fe64823ee136ac62bb9c2660bc1aacb"
],
[
"e",
"001eeab32652a45c193be16dfbe4460792c4771e555306421f3c05d02805a1b1"
],
[
"p",
"e1ff3bfdd4e40315959b08b4fcc8245eaa514637e1d4ec2ae166b743341be1af"
],
[
"p",
"b2dd40097e4d04b1a56fb3b65fc1d1aaf2929ad30fd842c74d68b9908744495b"
]
],
"content": "It’s simply not compatible.\n\nNIP57 zap mandates that the description hash of the invoice has to be the zap request note, whereas conventional with LNURL-pay invoices, it’s the LNURL-pay metadata that should be the desc hash.\n\nSo basically a zap is not really using LNURL-pay, it’s just the same URL endpoint.\nSo now all LNURL-pay servers has to also support this new propertary protocol.\n\nIf we’re going to think long-term, this can have some seriously bad implications, as both LNURL-pay and NIP57 progresses and moves forward.\n\nBut I can give you a clear-cut example: LUD-18 (https://github.com/lnurl/luds/blob/luds/18.md) also let’s you commit arbitrary payer identities to a payment (which is the primary goal of NIP57).\nBut seeing how NIP57 takes precedence, there’s no way to use NIP57 and LUD-18 at the same time, which is just sad.\n\nTo make things in the right way, zaps should’ve just used the already specified and established way to commit data, which is LUD-18.",
"sig": "92f967e6f5fb8e50ea3e41b2f18ae8d71b99c868ad521899cfbe43a459368f0bf374f616df53304340f5c01fc5417a73a88182e1b0b11fbe0a70b734b883e3a9"
}