Subnostr

Replying to

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 ?

bumi 1y ago

assuming a zap request could be shorter than 639 bytes it would also not work.

I don’t know the bolt11 details well enough.

Even if it’s their fault to not implement the bolt11 spec perfectly the state is that some big implementations have this problem.

It limits how zappers can be built. LN implementations have problems, not to talk about tools like lnbits, strike, etc.

those can not be used because of this limitation.

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

So you just want nip57 to be updated to remove this:

SHA256(description) MUST match the description hash in the bolt11 invoice.

bumi 1y ago

basically, yes. making this independent of the bolt11 somehow to allow implementations that have issues with the description hash also be used to receive zaps.

bumi 1y ago

I mainly was curious what’s the reason or if I miss something on why it is in there. (just as lnurl itself has removed it)