bumi on Nostr: why should nostr clients check the description hash of the bolt11 in the zap? What ...
why should nostr clients check the description hash of the bolt11 in the zap?
What does this prevent/allow?
I am asking because we dropped the description hash in the lnurl.
And some ln implementations have issues with the description hash.
cc
jb55 (npub1xts…kk5s) calle 👁️⚡👁️ (npub12rv…85vg)Published at
2024-04-18 07:23:51Event JSON
{
"id": "a897b098bf1bb8c006042f35080811ce6cae48432e4aadd13cf9fdfc217d035c",
"pubkey": "330fb1431ff9d8c250706bbcdc016d5495a3f744e047a408173e92ae7ee42dac",
"created_at": 1713425031,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"",
"mention"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63",
"",
"mention"
]
],
"content": "why should nostr clients check the description hash of the bolt11 in the zap? \nWhat does this prevent/allow? \n\nI am asking because we dropped the description hash in the lnurl. \nAnd some ln implementations have issues with the description hash.\n\ncc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg",
"sig": "bc46ea6b6470188b82c43e7b9170aeb1bc936eef094368e40ee503546f77c3939c414a7f8c1a0e475dcf63fb7a7536020e2adfbb13156c06a731cf420f6ae52c"
}
