bumi on Nostr: one issue is that this usage of the description hash is not the intended usage by the ...
one issue is that this usage of the description hash is not the intended usage by the bolt11 spec and by the node implementations. (LDK, CLN, Phoenix) (e.g a phoenix or LDK backed zap receiver can not work because of that)
Then I feel like this is also a very indirect and complicated check (decoding the bolt11, getting the hash, hashing the request,…) and it seems like damus is the only client doing this.
can we make this independent of the bolt11 somehow?
Published at
2024-04-18 10:20:24Event JSON
{
"id": "841ecb64aa8726a3d4d19882b23a23a9ed38429b9468bb744d3b01175a27cbb1",
"pubkey": "330fb1431ff9d8c250706bbcdc016d5495a3f744e047a408173e92ae7ee42dac",
"created_at": 1713435624,
"kind": 1,
"tags": [
[
"e",
"a897b098bf1bb8c006042f35080811ce6cae48432e4aadd13cf9fdfc217d035c"
],
[
"e",
"83d36d43e898cabea74fe543bfd9145b4d3c62efea8fdbf3b8e97e92204d2d99"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
]
],
"content": "one issue is that this usage of the description hash is not the intended usage by the bolt11 spec and by the node implementations. (LDK, CLN, Phoenix) (e.g a phoenix or LDK backed zap receiver can not work because of that)\n\nThen I feel like this is also a very indirect and complicated check (decoding the bolt11, getting the hash, hashing the request,…) and it seems like damus is the only client doing this.\n\ncan we make this independent of the bolt11 somehow?",
"sig": "8ac6069f6d35c5841b1574177f3e0c41fee4b1495f983e8d0df66d7fc3b920e2c0a3b13c99934fc20117fae7774c8006278a7fdacc21813d74576274591b2cae"
}
