Replying to Avatar jb55

If nodes aren’t doing this they are not following spec?

bolt11: “a reader …. MUST check that the sha2 256-bit hash in the `h` field exactly matches the hashed description “

How can it do this without storing the description when creating deschash invoices ?
Avatar
bumi 1y ago

the reader is the sender’s wallet, right?

this is not a real world case.

that mean for example WoS, etc. would need to somehow also know the zap request to do that check.

Reply to this note

Please Login to reply.

Discussion

Avatar
jb55 1y ago

this is problem with the ecosystem atm, there is no way to pass a description into the wallet via a lightning link, i added this to my CLN ios wallet but it seems no other wallet does this. It definitely seems like people are not caring about the spec and are just paying deschash invoices without the description… maybe just have to live with that now ?

Avatar
bumi 1y ago

even if one would pass some random big string to the wallet, what should it do with the zap request for example? (bolt11 and description would come from the same source)

should it show the scary JSON somehow to the user?

the description is used as a short text for humans. that’s what is shown for people.

Avatar
jb55 1y ago

yes the wallet would have to support parsing that and show a cool zap screen, which isn’t too unreasonable considering the amount of overlap these days. But definitely not good for a general wallet. I imagine people will put lots of weird crap in bolt11 descriptions 😬